Skip to content

1.39.0 (#152)#153

Merged
Dargon789 merged 1 commit intomasterfrom
1.39.0
Mar 2, 2026
Merged

1.39.0 (#152)#153
Dargon789 merged 1 commit intomasterfrom
1.39.0

Conversation

@Dargon789
Copy link
Copy Markdown
Owner

  • feat: support to install the latest version

  • chore: test & fmt & clippy

  • docs: update command docs

  • docs: update command docs

  • Create warm-rice-appear.md

  • Update change set to be a minor release

As this is a new feature

  • chore: update workflow to install pnpm

  • Remove feat: from changeset

Because GitHub actions approval button is missing

  • run pnpm like other tasks

  • Revert "run pnpm like other tasks"

This reverts commit f5f2ca2. we can revert the yarn changes and do it in a different PR

  • revert the changes in .github/workflows

  • feat: add remote version sorting and filtering

  • use UserVersion for filtering

  • add additional lts filter

  • refactor: use Vec::retain instead of filtering and collecting

  • fix docstring for sort option

  • change docstring for filter argument

  • refactor vec filtering

  • refactor to use sort_by_key and reverse

  • add latest flag

  • make filter an option as well

  • move sort into command as it is presentational

  • fix getting latest version

  • refactors

  • update docs/commands.md

  • sort upon installation

  • fix clippy

  • don't mention rust structs in the cli docs

  • post a token example

  • welp

  • chore(deps): update actions/setup-node action to v4

  • chore(deps): update pnpm to v9

  • update devDependencies

  • test more stuff in archiving

  • fnm env --global: considering if this is a good idea

technically i think that i can just mutate the 'default' alias instead. because now that i think about it, it makes 0 sense to set current to 'default' every time a new shell is opened. so current is default.

  • recovery version corepack

[email protected]

Bumps the cargo group with 1 update in the / directory: ring.

Updates ring from 0.17.8 to 0.17.13


updated-dependencies:

  • dependency-name: ring dependency-type: indirect dependency-group: cargo ...

Bumps the github_actions group with 1 update in the /.github/workflows directory: dawidd6/action-download-artifact.

Updates dawidd6/action-download-artifact from 2 to 6


updated-dependencies:

  • dependency-name: dawidd6/action-download-artifact dependency-type: direct:production dependency-group: github_actions ...

This reverts commit b454d73.

  • Bump tokio from 1.37.0 to 1.42.0 in the cargo group across 1 directory

Bumps the cargo group with 1 update in the / directory: tokio.

Updates tokio from 1.37.0 to 1.42.0


updated-dependencies:

  • dependency-name: tokio dependency-version: 1.42.0 dependency-type: indirect dependency-group: cargo ...

Bumps the cargo group with 1 update in the / directory: tokio.

Updates tokio from 1.42.0 to 1.42.1


updated-dependencies:

  • dependency-name: tokio dependency-version: 1.42.1 dependency-type: indirect dependency-group: cargo ...

Bumps the github_actions group with 1 update in the /.github/workflows directory: dawidd6/action-download-artifact.

Updates dawidd6/action-download-artifact from 2 to 6


updated-dependencies:

  • dependency-name: dawidd6/action-download-artifact dependency-version: '6' dependency-type: direct:production dependency-group: github_actions ...

Snyk has created this PR to upgrade which from 3.0.1 to 5.0.0.

See this package in npm:
which

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade @changesets/cli from 2.27.5 to 2.28.1.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade prettier from 3.3.0 to 3.5.3.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade execa from 7.2.0 to 9.5.2.

See this package in npm:
execa

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade @types/node from 18.19.87 to 22.14.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade @changesets/cli from 2.28.1 to 2.29.1.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

  • fix: upgrade @changesets/cli from 2.29.1 to 2.29.2

Snyk has created this PR to upgrade @changesets/cli from 2.29.1 to 2.29.2.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

  • chore(deps): update rust crate embed-resource to v2.5.2

  • fix(deps): update rust crate tar to v0.4.44

  • fix(deps): update rust crate thiserror to v1.0.69

  • chore(deps): update rust crate indoc to v2.0.7

  • Create weak-moose-love.md

  • Update .changeset/weak-moose-love.md

  • Create config.yml (Create config.yml #64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup. Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'. Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job. Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.

Chores:
Add a new changeset file for fnm patch release

Bumps the cargo group with 4 updates in the / directory: hashbrown, ring, rustls and tokio.

Updates hashbrown from 0.15.0 to 0.15.3

Updates ring from 0.17.8 to 0.17.14

Updates rustls from 0.23.16 to 0.23.23

Updates tokio from 1.41.0 to 1.42.1


updated-dependencies:

  • dependency-name: hashbrown dependency-version: 0.15.3 dependency-type: indirect dependency-group: cargo
  • dependency-name: ring dependency-version: 0.17.14 dependency-type: indirect dependency-group: cargo
  • dependency-name: rustls dependency-version: 0.23.23 dependency-type: indirect dependency-group: cargo
  • dependency-name: tokio dependency-version: 1.42.1 dependency-type: indirect dependency-group: cargo ...
  • chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates

Bumps the npm_and_yarn group with 2 updates in the / directory: @babel/helpers and @babel/runtime.

Updates @babel/helpers from 7.26.0 to 7.27.4

Updates @babel/runtime from 7.26.0 to 7.27.4


updated-dependencies:

  • dependency-name: "@babel/helpers" dependency-version: 7.27.4 dependency-type: indirect dependency-group: npm_and_yarn
  • dependency-name: "@babel/runtime" dependency-version: 7.27.4 dependency-type: indirect dependency-group: npm_and_yarn ...

The following vulnerabilities are fixed with an upgrade:

  • chore(deps): bump brace-expansion

Bumps the npm_and_yarn group with 1 update in the / directory: brace-expansion.

Updates brace-expansion from 1.1.11 to 1.1.12


updated-dependencies:

  • dependency-name: brace-expansion dependency-version: 1.1.12 dependency-type: indirect dependency-group: npm_and_yarn ...

Snyk has created this PR to upgrade zod from 3.25.76 to 4.0.0.

See this package in npm:
zod

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade @types/jest from 29.5.14 to 30.0.0.

See this package in npm:
@types/jest

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade prettier from 3.5.1 to 3.5.3.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade cross-env from 7.0.3 to 10.0.0.

See this package in npm:
cross-env

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade prettier from 3.5.3 to 3.6.2.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade @types/node from 18.19.123 to 24.1.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

The following vulnerabilities are fixed with an upgrade:

  • Create label.yml (Create label.yml #40)

  • Create label.yml

  • Potential fix for code scanning alert no. 30: Workflow does not contain permissions


Bumps the cargo group with 1 update in the / directory: tracing-subscriber.

Updates tracing-subscriber from 0.3.18 to 0.3.20


updated-dependencies:

  • dependency-name: tracing-subscriber dependency-version: 0.3.20 dependency-type: indirect dependency-group: cargo ...

Snyk has created this PR to upgrade @changesets/cli from 2.29.6 to 2.29.7.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

  • Update package.json

Snyk has created this PR to upgrade cmd-ts from 0.13.0 to 0.14.1.

See this package in npm:
cmd-ts

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade p-retry from 6.2.1 to 7.0.0.

See this package in npm:
p-retry

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Bumps the cargo group with 1 update in the / directory: zip.

Updates zip from 2.2.0 to 6.0.0


updated-dependencies:

  • dependency-name: zip dependency-version: 6.0.0 dependency-type: direct:production dependency-group: cargo ...

CI:

Modify the Publish to crates.io step to use cargo publish --dry-run

Add a changeset for fnm to patch-release the package and update the release-to-cargo workflow configuration to use the master branch

Bug Fixes:

Update release-to-cargo.yml config to use the master branch Chores:

Add angry-moose-hug changeset to bump fnm patch version

  • Update .changeset/angry-moose-hug.md

New Changeset File: A new changeset file, "angry-moose-hug.md", has been added to the ".changeset" directory, indicating a recorded change for release management.
Release Configuration Update: The changeset documents a "patch" type change for "fnm", specifically a fix to update the "release-to-cargo.yml" configuration to use "base:br master".


Update release-to-cargo.yml workflow config to use master as the base branch for fnm

  • Update .changeset/funny-falcons-breathe.md

Streamline the release workflow by restricting triggers to master and main branches and pin Node.js to version 22.

CI:

Remove the 'dev' branch from the release workflow triggers Pin Node.js version to 22 in the release job

Add CircleCI pipeline to build, test, and format-check the Rust project with caching for dependencies

CI:

Introduce a CircleCI config (.circleci/ci.yml) using cimg/rust:1.89.0 Run cargo fmt -- --check and cargo test in a single build-and-test job Cache Cargo dependencies and build artifacts between builds

CI:

Add .circleci/ci-say-hello.yml with a say-hello job using cimg/base:current and a workflow to run it

Add .circleci/ci-foundry.yml to scaffold a new CircleCI pipeline with a custom Docker executor, a CI job, and a workflow.

CI:

Add initial CircleCI pipeline configuration using version 2.1 Define custom executor with Docker image and Docker Hub credentials Introduce job 'web3-defi-game-project-' with checkout and placeholder run step Add workflow 'my-custom-workflow' to orchestrate the CI job

Restructure the CircleCI configuration by removing the custom executor, adding a sample say-hello job and workflow, and enhancing the file with explanatory comments CI:
Remove custom executor and replace it with a basic say-hello job using the cimg/base:current Docker image Introduce a say-hello-workflow to orchestrate the new job Documentation:

Add inline comments to guide configuration of executors, jobs, steps, and workflows in the CI file

Add a SECURITY.md file to establish the project's security policy, detail supported versions, and outline the vulnerability reporting process.

Documentation:

Introduce SECURITY.md with a security policy and supported versions table Include guidelines for reporting vulnerabilities and expected response procedures

  • Update SECURITY.md

  • Update SECURITY.md


CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup. Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'. Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job. Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


CI:
Delete .circleci/ci-say-hello.yml to clean up unused CI pipeline

CI:
Use cimg/rust:1.88.0 instead of cimg/rust:1.89.0 in the CI configuration https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the CircleCI configuration to use Rust version 1.88.0, aligning it with the rust-toolchain.toml file. This is a good correction. I have provided one suggestion to use a more flexible image tag to better match the behavior of rustup with the toolchain file, which will improve the long-term maintainability of the CI setup.

Switch the GitHub Action for releasing to crates.io from a dry run to a real publish and clean up unused permissions settings. CI:
Remove redundant permissions block from the release-to-cargo workflow Replace dry-run with actual cargo publish command


CI:
Remove 'dev' branch from rust.yml workflow triggers

Add a new GitHub Actions workflow (docker.yml) to automate building, pushing, and signing Docker images via Buildx, metadata extraction, and cosign integration

New Features:

Introduce a Docker CI workflow triggered on schedule, push to master, and semantic version tags, as well as on pull requests Build and push multi-platform Docker images to GHCR using Buildx with dynamic tagging Integrate cosign to sign published Docker images using Sigstore identity tokens Enhancements:

Set up Docker metadata action for tag and label generation Enable caching strategies for faster builds using GitHub Actions CI:

Add .github/workflows/docker.yml to define the Docker build and publish pipeline Chores:

Configure environment variables for registry (GHCR) and image naming based on the repository

Refine the GitHub Actions rust.yml workflow by restricting triggers to the master branch, pinning Node.js to version 18.x across all setup-node steps, and cleaning up formatting and commented version entries. CI:

Limit workflow triggers to the master branch only
Pin Node.js setup in all jobs to version 18.x, removing 20.x and 22.x entries Remove redundant commented Node.js version lines and extra blank lines

Bumps the npm_and_yarn group with 1 update in the / directory: js-yaml.

Updates js-yaml from 3.14.1 to 3.14.2


updated-dependencies:

  • dependency-name: js-yaml dependency-version: 3.14.2 dependency-type: indirect dependency-group: npm_and_yarn ...
  • Create lazy-snails-return.md (Create lazy-snails-return.md #81)

  • Create lazy-snails-return.md Chores:
    Create a new .changeset file to bump the patch version for fnm with a note about fixing the release-to-cargo.yml configuration.

  • Update .changeset/lazy-snails-return.md Highlights
    Changeset Addition: A new changeset file, lazy-snails-return.md, has been added. This file documents a fix related to the release-to-cargo.yml configuration. Configuration Fix: The changeset entry specifically notes an update to the release-to-cargo.yml configuration, setting its base to br master.


CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup. Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'. Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job. Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.

Chores:
Add a new changeset file for fnm patch release


Code Formatting: Removed an unnecessary blank line in tests/proxy-server/index.mjs to improve code consistency.

Add a GitHub Actions workflow to build and deploy the application to Google Kubernetes Engine via Google Cloud. Build:
Introduce a Google Cloud–oriented workflow that builds a Docker image and pushes it to Artifact Registry on pushes to the main branch. CI:
Add a GitHub Actions pipeline that authenticates with Google Cloud using Workload Identity Federation and runs container build and deployment steps. Deployment:
Automate deploying the built Docker image to a GKE cluster using kustomize and kubectl.


Dargon789/uniswap.app@011f260

  • Update package.json

  • Update README.md (Update README.md #94)

  • Update README.md

  • Update README.md

  • Update README.md

  • Update README.md

  • Update README.md

  • Update README.md

  • Update README.md

  • Update README.md


Dargon789/circleci-docs@cd854b0

Dargon789/foundry@fcfa587

  • Update Cargo.toml

CI:

Adjust GitHub Actions label workflow triggers to use the 'main' branch for push events while keeping pull request triggers on 'master'.

  • fix(deps): update all non-major dependencies

  • Add build artifacts and fnm.exe to repository

This commit adds the .fnm/fnm.exe binary and various Rust build artifacts under target-wsl/, including .rustc_info.json, CACHEDIR.TAG, and debug fingerprints for dependencies. These files appear to be generated as part of a Rust build process, possibly for debugging or distribution purposes.


  • Update README.md

  • Update .github/ISSUE_TEMPLATE/bug_report.md

  • Update .github/ISSUE_TEMPLATE/bug_report.md


sixty-rice-do.md

  • Update Cargo.toml

  • Update Cargo.toml

  • Update SECURITY.md

  • Update src/hooks.rs

  • Update test-hooks-integration.sh

  • Create SECURITY.md #1.39.0 (#1.39.0 #123)

  • Make install.sh tee instead of echoing twice

Also, fish bit was the only one that didn't print a newline to $CONF_FILE, now they're all the same.

  • Check if fnm is installed before shell setup

Change $CONF_FILE append strings to check whether $INSTALL_DIR exists before doing any setup. This way whenever a user syncs their shell config across machines, the machines without fnm installed won't throw errors.

Snyk has created this PR to upgrade cross-env from 7.0.3 to 10.0.0.

See this package in npm:
cross-env

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade prettier from 3.5.3 to 3.6.2.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade @types/node from 18.19.123 to 24.1.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

The following vulnerabilities are fixed with an upgrade:

  • Create label.yml (Create label.yml #40)

  • Create label.yml

  • Potential fix for code scanning alert no. 30: Workflow does not contain permissions


Bumps the cargo group with 1 update in the / directory: tracing-subscriber.

Updates tracing-subscriber from 0.3.18 to 0.3.20


updated-dependencies:

  • dependency-name: tracing-subscriber dependency-version: 0.3.20 dependency-type: indirect dependency-group: cargo ...

  • Adjust install script for POSIX compliance

  • Create temporary directory when mktemp is unavailable

  • Use "dot" instead of source builtin when shell is not fish

  • Inform the user where fnm is being installed

  • [Snyk] Upgrade @changesets/cli from 2.29.6 to 2.29.7 ([Snyk] Upgrade @changesets/cli from 2.29.6 to 2.29.7 #46)

  • fix: upgrade @changesets/cli from 2.29.6 to 2.29.7

Snyk has created this PR to upgrade @changesets/cli from 2.29.6 to 2.29.7.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

  • Update package.json

Snyk has created this PR to upgrade cmd-ts from 0.13.0 to 0.14.1.

See this package in npm:
cmd-ts

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Snyk has created this PR to upgrade p-retry from 6.2.1 to 7.0.0.

See this package in npm:
p-retry

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Bumps the cargo group with 1 update in the / directory: zip.

Updates zip from 2.2.0 to 6.0.0


updated-dependencies:

  • dependency-name: zip dependency-version: 6.0.0 dependency-type: direct:production dependency-group: cargo ...
  • Create smart-avocados-try.md (Create smart-avocados-try.md #48)

  • Create smart-avocados-try.md

  • Update .changeset/smart-avocados-try.md New Changeset File: A new changeset file, smart-avocados-try.md, has been added to the .changeset directory. This file is used to record a specific change for future release notes or changelog generation. Patch Metadata: The newly added changeset file includes front matter metadata specifying "fnm": "patch", indicating the type of change being recorded.


CI:

Modify the Publish to crates.io step to use cargo publish --dry-run

Add a changeset for fnm to patch-release the package and update the release-to-cargo workflow configuration to use the master branch

Bug Fixes:

Update release-to-cargo.yml config to use the master branch Chores:

Add angry-moose-hug changeset to bump fnm patch version

  • Update .changeset/angry-moose-hug.md

New Changeset File: A new changeset file, "angry-moose-hug.md", has been added to the ".changeset" directory, indicating a recorded change for release management.
Release Configuration Update: The changeset documents a "patch" type change for "fnm", specifically a fix to update the "release-to-cargo.yml" configuration to use "base:br master".


Update release-to-cargo.yml workflow config to use master as the base branch for fnm

  • Update .changeset/funny-falcons-breathe.md

Streamline the release workflow by restricting triggers to master and main branches and pin Node.js to version 22.

CI:

Remove the 'dev' branch from the release workflow triggers Pin Node.js version to 22 in the release job

Add CircleCI pipeline to build, test, and format-check the Rust project with caching for dependencies

CI:

Introduce a CircleCI config (.circleci/ci.yml) using cimg/rust:1.89.0 Run cargo fmt -- --check and cargo test in a single build-and-test job Cache Cargo dependencies and build artifacts between builds

CI:

Add .circleci/ci-say-hello.yml with a say-hello job using cimg/base:current and a workflow to run it

Add .circleci/ci-foundry.yml to scaffold a new CircleCI pipeline with a custom Docker executor, a CI job, and a workflow.

CI:

Add initial CircleCI pipeline configuration using version 2.1 Define custom executor with Docker image and Docker Hub credentials Introduce job 'web3-defi-game-project-' with checkout and placeholder run step Add workflow 'my-custom-workflow' to orchestrate the CI job

Restructure the CircleCI configuration by removing the custom executor, adding a sample say-hello job and workflow, and enhancing the file with explanatory comments CI:
Remove custom executor and replace it with a basic say-hello job using the cimg/base:current Docker image Introduce a say-hello-workflow to orchestrate the new job Documentation:

Add inline comments to guide configuration of executors, jobs, steps, and workflows in the CI file

Add a SECURITY.md file to establish the project's security policy, detail supported versions, and outline the vulnerability reporting process.

Documentation:

Introduce SECURITY.md with a security policy and supported versions table Include guidelines for reporting vulnerabilities and expected response procedures

  • Update SECURITY.md

  • Update SECURITY.md


CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup. Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'. Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job. Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


CI:
Delete .circleci/ci-say-hello.yml to clean up unused CI pipeline

CI:
Use cimg/rust:1.88.0 instead of cimg/rust:1.89.0 in the CI configuration https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the CircleCI configuration to use Rust version 1.88.0, aligning it with the rust-toolchain.toml file. This is a good correction. I have provided one suggestion to use a more flexible image tag to better match the behavior of rustup with the toolchain file, which will improve the long-term maintainability of the CI setup.

Switch the GitHub Action for releasing to crates.io from a dry run to a real publish and clean up unused permissions settings. CI:
Remove redundant permissions block from the release-to-cargo workflow Replace dry-run with actual cargo publish command


CI:
Remove 'dev' branch from rust.yml workflow triggers

Add a new GitHub Actions workflow (docker.yml) to automate building, pushing, and signing Docker images via Buildx, metadata extraction, and cosign integration

New Features:

Introduce a Docker CI workflow triggered on schedule, push to master, and semantic version tags, as well as on pull requests Build and push multi-platform Docker images to GHCR using Buildx with dynamic tagging Integrate cosign to sign published Docker images using Sigstore identity tokens Enhancements:

Set up Docker metadata action for tag and label generation Enable caching strategies for faster builds using GitHub Actions CI:

Add .github/workflows/docker.yml to define the Docker build and publish pipeline Chores:

Configure environment variables for registry (GHCR) and image naming based on the repository

Refine the GitHub Actions rust.yml workflow by restricting triggers to the master branch, pinning Node.js to version 18.x across all setup-node steps, and cleaning up formatting and commented version entries. CI:

Limit workflow triggers to the master branch only
Pin Node.js setup in all jobs to version 18.x, removing 20.x and 22.x entries Remove redundant commented Node.js version lines and extra blank lines

Bumps the npm_and_yarn group with 1 update in the / directory: js-yaml.

Updates js-yaml from 3.14.1 to 3.14.2


updated-dependencies:

  • dependency-name: js-yaml dependency-version: 3.14.2 dependency-type: indirect dependency-group: npm_and_yarn ...

Chores:
Create a spotty-weeks-sit changeset specifying a patch release for fnm

  • Create lazy-snails-return.md (Create lazy-snails-return.md #81)

  • Create lazy-snails-return.md Chores:
    Create a new .changeset file to bump the patch version for fnm with a note about fixing the release-to-cargo.yml configuration.

  • Update .changeset/lazy-snails-return.md Highlights
    Changeset Addition: A new changeset file, lazy-snails-return.md, has been added. This file documents a fix related to the release-to-cargo.yml configuration. Configuration Fix: The changeset entry specifically notes an update to the release-to-cargo.yml configuration, setting its base to br master.


CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup. Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'. Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job. Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.

Chores:
Add a new changeset file for fnm patch release


Code Formatting: Removed an unnecessary blank line in tests/proxy-server/index.mjs to improve code consistency.

Add a GitHub Actions workflow to build and deploy the application to Google Kubernetes Engine via Google Cloud. Build:
Introduce a Google Cloud–oriented workflow that builds a Docker image and pushes it to Artifact Registry on pushes to the main branch. CI:
Add a GitHub Actions pipeline that authenticates with Google Cloud using Workload Identity Federation and runs container build and deployment steps. Deployment:
Automate deploying the built Docker image to a GKE cluster using kustomize and kubectl.


* feat: support to install the latest version

* chore: test & fmt & clippy

* docs: update command docs

* docs: update command docs

* Create warm-rice-appear.md

* Update change set to be a minor release

As this is a new feature

* chore: update workflow to install pnpm

* Remove `feat:` from changeset

Because GitHub actions approval button is missing

* run pnpm like other tasks

* Revert "run pnpm like other tasks"

This reverts commit f5f2ca29f17a3440d576085ec34d4644d56a48e4.
we can revert the yarn changes and do it in a different PR

* revert the changes in .github/workflows

* feat: add remote version sorting and filtering

* use `UserVersion` for filtering

* add additional lts filter

* refactor: use `Vec::retain` instead of filtering and collecting

* fix docstring for sort option

* change docstring for filter argument

* refactor vec filtering

Co-authored-by: Brennan Kinney <[email protected]>

* refactor to use `sort_by_key` and `reverse`

Co-authored-by: Brennan Kinney <[email protected]>

* add latest flag

* make filter an option as well

* move sort into command as it is presentational

* fix getting latest version

* refactors

* update docs/commands.md

* sort upon installation

* fix clippy

* don't mention rust structs in the cli docs

* post a token example

* welp

* chore(deps): update actions/setup-node action to v4

* chore(deps): update pnpm to v9

* update devDependencies

* test more stuff in archiving

* fnm env --global: considering if this is a good idea

technically i think that i can just mutate the 'default' alias instead. because now that i think about it,
it makes 0 sense to set current to 'default' every time a new shell is opened. so current _is_ default.

* recovery version corepack

[email protected]

* Circleci project setup (#4)

* Add .circleci/config.yml

* Add .circleci/config.yml

* Add .circleci/config.yml

* Bump ring from 0.17.8 to 0.17.13 in the cargo group across 1 directory (#3)

Bumps the cargo group with 1 update in the / directory: [ring](https://github.com/briansmith/ring).


Updates `ring` from 0.17.8 to 0.17.13
- [Changelog](https://github.com/briansmith/ring/blob/main/RELEASES.md)
- [Commits](https://github.com/briansmith/ring/commits)

---
updated-dependencies:
- dependency-name: ring
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: AU_gdev_19 <[email protected]>

* Bump dawidd6/action-download-artifact (#2)

Bumps the github_actions group with 1 update in the /.github/workflows directory: [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact).


Updates `dawidd6/action-download-artifact` from 2 to 6
- [Release notes](https://github.com/dawidd6/action-download-artifact/releases)
- [Commits](https://github.com/dawidd6/action-download-artifact/compare/v2...v6)

---
updated-dependencies:
- dependency-name: dawidd6/action-download-artifact
  dependency-type: direct:production
  dependency-group: github_actions
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: AU_gdev_19 <[email protected]>

* Create SECURITY.md (#1)

Signed-off-by: AU_gdev_19 <[email protected]>

* Revert "Bump dawidd6/action-download-artifact (#2)" (#5)

This reverts commit b454d73a9022373d51a80f5a33813c58e4dff91d.

* Bump tokio from 1.37.0 to 1.42.0 in the cargo group across 1 directory

Bumps the cargo group with 1 update in the / directory: [tokio](https://github.com/tokio-rs/tokio).


Updates `tokio` from 1.37.0 to 1.42.0
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](https://github.com/tokio-rs/tokio/compare/tokio-1.37.0...tokio-1.42.0)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.42.0
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>

* Bump tokio from 1.42.0 to 1.42.1 in the cargo group across 1 directory (#8)

Bumps the cargo group with 1 update in the / directory: [tokio](https://github.com/tokio-rs/tokio).


Updates `tokio` from 1.42.0 to 1.42.1
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](https://github.com/tokio-rs/tokio/compare/tokio-1.42.0...tokio-1.42.1)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.42.1
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump dawidd6/action-download-artifact (#7)

Bumps the github_actions group with 1 update in the /.github/workflows directory: [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact).


Updates `dawidd6/action-download-artifact` from 2 to 6
- [Release notes](https://github.com/dawidd6/action-download-artifact/releases)
- [Commits](https://github.com/dawidd6/action-download-artifact/compare/v2...v6)

---
updated-dependencies:
- dependency-name: dawidd6/action-download-artifact
  dependency-version: '6'
  dependency-type: direct:production
  dependency-group: github_actions
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: AU_gdev_19 <[email protected]>

* Create wet-donkeys-jump.md

Signed-off-by: AU_gdev_19 <[email protected]>

* feat: upgrade which from 3.0.1 to 5.0.0 (#17)

Snyk has created this PR to upgrade which from 3.0.1 to 5.0.0.

See this package in npm:
which

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* fix: upgrade @changesets/cli from 2.27.5 to 2.28.1 (#16)

Snyk has created this PR to upgrade @changesets/cli from 2.27.5 to 2.28.1.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* fix: upgrade prettier from 3.3.0 to 3.5.3 (#15)

Snyk has created this PR to upgrade prettier from 3.3.0 to 3.5.3.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* feat: upgrade execa from 7.2.0 to 9.5.2 (#14)

Snyk has created this PR to upgrade execa from 7.2.0 to 9.5.2.

See this package in npm:
execa

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* feat: upgrade @types/node from 18.19.87 to 22.14.0 (#13)

Snyk has created this PR to upgrade @types/node from 18.19.87 to 22.14.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* fix: upgrade @changesets/cli from 2.28.1 to 2.29.1 (#19)

Snyk has created this PR to upgrade @changesets/cli from 2.28.1 to 2.29.1.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* fix: upgrade @changesets/cli from 2.29.1 to 2.29.2

Snyk has created this PR to upgrade @changesets/cli from 2.29.1 to 2.29.2.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

* chore(deps): update rust crate embed-resource to v2.5.2

* fix(deps): update rust crate tar to v0.4.44

* fix(deps): update rust crate thiserror to v1.0.69

* chore(deps): update rust crate indoc to v2.0.7

* Create weak-moose-love.md

Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/weak-moose-love.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.
Signed-off-by: Dargon789 <[email protected]>

* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release
Signed-off-by: Dargon789 <[email protected]>

* Add changeset for updating indoc crate to v2.0.7 (#101)

Signed-off-by: Dargon789 <[email protected]>

* Update Cargo.toml (#98)  (#104)

* chore(deps): bump the cargo group across 1 directory with 4 updates

Bumps the cargo group with 4 updates in the / directory: [hashbrown](https://github.com/rust-lang/hashbrown), [ring](https://github.com/briansmith/ring), [rustls](https://github.com/rustls/rustls) and [tokio](https://github.com/tokio-rs/tokio).


Updates `hashbrown` from 0.15.0 to 0.15.3
- [Release notes](https://github.com/rust-lang/hashbrown/releases)
- [Changelog](https://github.com/rust-lang/hashbrown/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rust-lang/hashbrown/compare/v0.15.0...v0.15.3)

Updates `ring` from 0.17.8 to 0.17.14
- [Changelog](https://github.com/briansmith/ring/blob/main/RELEASES.md)
- [Commits](https://github.com/briansmith/ring/commits)

Updates `rustls` from 0.23.16 to 0.23.23
- [Release notes](https://github.com/rustls/rustls/releases)
- [Changelog](https://github.com/rustls/rustls/blob/main/CHANGELOG.md)
- [Commits](https://github.com/rustls/rustls/compare/v/0.23.16...v/0.23.23)

Updates `tokio` from 1.41.0 to 1.42.1
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](https://github.com/tokio-rs/tokio/compare/tokio-1.41.0...tokio-1.42.1)

---
updated-dependencies:
- dependency-name: hashbrown
  dependency-version: 0.15.3
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: ring
  dependency-version: 0.17.14
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: rustls
  dependency-version: 0.23.23
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: tokio
  dependency-version: 1.42.1
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>

* chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates

Bumps the npm_and_yarn group with 2 updates in the / directory: [@babel/helpers](https://github.com/babel/babel/tree/HEAD/packages/babel-helpers) and [@babel/runtime](https://github.com/babel/babel/tree/HEAD/packages/babel-runtime).


Updates `@babel/helpers` from 7.26.0 to 7.27.4
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.27.4/packages/babel-helpers)

Updates `@babel/runtime` from 7.26.0 to 7.27.4
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.27.4/packages/babel-runtime)

---
updated-dependencies:
- dependency-name: "@babel/helpers"
  dependency-version: 7.27.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@babel/runtime"
  dependency-version: 7.27.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>

* Potential fix for code scanning alert no. 3: Server-side request forgery

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <[email protected]>

* Potential fix for code scanning alert no. 19: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <[email protected]>

* fix: package.json to reduce vulnerabilities (#27)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-INFLIGHT-6095116

Co-authored-by: snyk-bot <[email protected]>

* chore(deps): bump brace-expansion

Bumps the npm_and_yarn group with 1 update in the / directory: [brace-expansion](https://github.com/juliangruber/brace-expansion).


Updates `brace-expansion` from 1.1.11 to 1.1.12
- [Release notes](https://github.com/juliangruber/brace-expansion/releases)
- [Commits](https://github.com/juliangruber/brace-expansion/compare/1.1.11...v1.1.12)

---
updated-dependencies:
- dependency-name: brace-expansion
  dependency-version: 1.1.12
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>

* Create config.yml (#34)

* feat: upgrade zod from 3.25.76 to 4.0.0 (#33)

Snyk has created this PR to upgrade zod from 3.25.76 to 4.0.0.

See this package in npm:
zod

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* feat: upgrade @types/jest from 29.5.14 to 30.0.0 (#32)

Snyk has created this PR to upgrade @types/jest from 29.5.14 to 30.0.0.

See this package in npm:
@types/jest

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* fix: upgrade prettier from 3.5.1 to 3.5.3 (#25)

Snyk has created this PR to upgrade prettier from 3.5.1 to 3.5.3.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* feat: upgrade cross-env from 7.0.3 to 10.0.0 (#39)

Snyk has created this PR to upgrade cross-env from 7.0.3 to 10.0.0.

See this package in npm:
cross-env

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* fix: upgrade prettier from 3.5.3 to 3.6.2 (#38)

Snyk has created this PR to upgrade prettier from 3.5.3 to 3.6.2.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* feat: upgrade @types/node from 18.19.123 to 24.1.0 (#36)

Snyk has created this PR to upgrade @types/node from 18.19.123 to 24.1.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* fix: package.json to reduce vulnerabilities (#35)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-TMP-11501554

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* Create label.yml (#40)

* Create label.yml

Signed-off-by: AU_gdev_19 <[email protected]>

* Potential fix for code scanning alert no. 30: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <[email protected]>

---------

Signed-off-by: AU_gdev_19 <[email protected]>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* Update release.yml (#41)

Signed-off-by: AU_gdev_19 <[email protected]>

* chore(deps): bump tracing-subscriber from 0.3.18 to 0.3.20 in the cargo group across 1 directory (#42)

* chore(deps): bump tracing-subscriber

Bumps the cargo group with 1 update in the / directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).


Updates `tracing-subscriber` from 0.3.18 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.18...tracing-subscriber-0.3.20)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>

* Update rust.yml (#43)

Signed-off-by: AU_gdev_19 <[email protected]>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: AU_gdev_19 <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: AU_gdev_19 <[email protected]>

* [Snyk] Upgrade @changesets/cli from 2.29.6 to 2.29.7 (#46)

* fix: upgrade @changesets/cli from 2.29.6 to 2.29.7

Snyk has created this PR to upgrade @changesets/cli from 2.29.6 to 2.29.7.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

* Update package.json

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: snyk-bot <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* fix: upgrade cmd-ts from 0.13.0 to 0.14.1 (#45)

Snyk has created this PR to upgrade cmd-ts from 0.13.0 to 0.14.1.

See this package in npm:
cmd-ts

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* feat: upgrade p-retry from 6.2.1 to 7.0.0 (#44)

Snyk has created this PR to upgrade p-retry from 6.2.1 to 7.0.0.

See this package in npm:
p-retry

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* chore(deps): bump zip in the cargo group across 1 directory (#47)

Bumps the cargo group with 1 update in the / directory: [zip](https://github.com/zip-rs/zip2).


Updates `zip` from 2.2.0 to 6.0.0
- [Release notes](https://github.com/zip-rs/zip2/releases)
- [Changelog](https://github.com/zip-rs/zip2/blob/master/CHANGELOG.md)
- [Commits](https://github.com/zip-rs/zip2/compare/v2.2.0...v6.0.0)

---
updated-dependencies:
- dependency-name: zip
  dependency-version: 6.0.0
  dependency-type: direct:production
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update release-to-cargo.yml (#55)

CI:

Modify the Publish to crates.io step to use cargo publish --dry-run
Signed-off-by: Dargon789 <[email protected]>

* Create angry-moose-hug.md (#56)

* Create angry-moose-hug.md

Add a changeset for fnm to patch-release the package and update the release-to-cargo workflow configuration to use the master branch

Bug Fixes:

Update release-to-cargo.yml config to use the master branch
Chores:

Add angry-moose-hug changeset to bump fnm patch version

Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/angry-moose-hug.md

New Changeset File: A new changeset file, "angry-moose-hug.md", has been added to the ".changeset" directory, indicating a recorded change for release management.
Release Configuration Update: The changeset documents a "patch" type change for "fnm", specifically a fix to update the "release-to-cargo.yml" configuration to use "base:br master".

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Create funny-falcons-breathe.md (#57)

* Create funny-falcons-breathe.md
Bug Fixes:

Update release-to-cargo.yml workflow config to use master as the base branch for fnm
Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/funny-falcons-breathe.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update release.yml (#59)

Streamline the release workflow by restricting triggers to master and main branches and pin Node.js to version 22.

CI:

Remove the 'dev' branch from the release workflow triggers
Pin Node.js version to 22 in the release job
Signed-off-by: Dargon789 <[email protected]>

* Create ci.yml (#60)

Add CircleCI pipeline to build, test, and format-check the Rust project with caching for dependencies

CI:

Introduce a CircleCI config (.circleci/ci.yml) using cimg/rust:1.89.0
Run cargo fmt -- --check and cargo test in a single build-and-test job
Cache Cargo dependencies and build artifacts between builds
Signed-off-by: Dargon789 <[email protected]>

* Create ci-say-hello.yml (#61)

CI:

Add .circleci/ci-say-hello.yml with a say-hello job using cimg/base:current and a workflow to run it
Signed-off-by: Dargon789 <[email protected]>

* Create ci-foundry.yml (#62)

Add .circleci/ci-foundry.yml to scaffold a new CircleCI pipeline with a custom Docker executor, a CI job, and a workflow.

CI:

Add initial CircleCI pipeline configuration using version 2.1
Define custom executor with Docker image and Docker Hub credentials
Introduce job 'web3-defi-game-project-' with checkout and placeholder run step
Add workflow 'my-custom-workflow' to orchestrate the CI job
Signed-off-by: Dargon789 <[email protected]>

* Update config.yml (#66)

Restructure the CircleCI configuration by removing the custom executor, adding a sample say-hello job and workflow, and enhancing the file with explanatory comments
CI:
Remove custom executor and replace it with a basic say-hello job using the cimg/base:current Docker image
Introduce a say-hello-workflow to orchestrate the new job
Documentation:

Add inline comments to guide configuration of executors, jobs, steps, and workflows in the CI file
Signed-off-by: Dargon789 <[email protected]>

* Create SECURITY.md (#67)

* Create SECURITY.md

Add a SECURITY.md file to establish the project's security policy, detail supported versions, and outline the vulnerability reporting process.

Documentation:

Introduce SECURITY.md with a security policy and supported versions table
Include guidelines for reporting vulnerabilities and expected response procedures
Signed-off-by: Dargon789 <[email protected]>

* Update SECURITY.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update SECURITY.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Dargon789 patch 2 (#65)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md

Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/weak-moose-love.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Delete .circleci/ci-say-hello.yml (#69)

CI:
Delete .circleci/ci-say-hello.yml to clean up unused CI pipeline
Signed-off-by: Dargon789 <[email protected]>

* Update ci.yml (#70)

CI:
Use cimg/rust:1.88.0 instead of cimg/rust:1.89.0 in the CI configuration
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the CircleCI configuration to use Rust version 1.88.0, aligning it with the rust-toolchain.toml file. This is a good correction. I have provided one suggestion to use a more flexible image tag to better match the behavior of rustup with the toolchain file, which will improve the long-term maintainability of the CI setup.
Signed-off-by: Dargon789 <[email protected]>

* Update release-to-cargo.yml

Signed-off-by: Dargon789 <[email protected]>

* Update release-to-cargo.yml (#72)

Switch the GitHub Action for releasing to crates.io from a dry run to a real publish and clean up unused permissions settings.
CI:
Remove redundant permissions block from the release-to-cargo workflow
Replace dry-run with actual cargo publish command
Signed-off-by: Dargon789 <[email protected]>

* Update grumpy-dingos-turn.md (#73)

Signed-off-by: Dargon789 <[email protected]>

* Update release.yml (#74)

* Update release.yml

Signed-off-by: Dargon789 <[email protected]>

* Update .github/workflows/release.yml

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>

* Update rust.yml (#75)

CI:
Remove 'dev' branch from rust.yml workflow triggers
Signed-off-by: Dargon789 <[email protected]>

* Create docker.yml (#76)

Add a new GitHub Actions workflow (docker.yml) to automate building, pushing, and signing Docker images via Buildx, metadata extraction, and cosign integration

New Features:

Introduce a Docker CI workflow triggered on schedule, push to master, and semantic version tags, as well as on pull requests
Build and push multi-platform Docker images to GHCR using Buildx with dynamic tagging
Integrate cosign to sign published Docker images using Sigstore identity tokens
Enhancements:

Set up Docker metadata action for tag and label generation
Enable caching strategies for faster builds using GitHub Actions
CI:

Add .github/workflows/docker.yml to define the Docker build and publish pipeline
Chores:

Configure environment variables for registry (GHCR) and image naming based on the repository
Signed-off-by: Dargon789 <[email protected]>

* Create CNAME

* Update rust.yml (#78)

Refine the GitHub Actions rust.yml workflow by restricting triggers to the master branch, pinning Node.js to version 18.x across all setup-node steps, and cleaning up formatting and commented version entries.
CI:

Limit workflow triggers to the master branch only
Pin Node.js setup in all jobs to version 18.x, removing 20.x and 22.x entries
Remove redundant commented Node.js version lines and extra blank lines
Signed-off-by: Dargon789 <[email protected]>

* chore(deps): bump js-yaml in the npm_and_yarn group across 1 directory (#77)

Bumps the npm_and_yarn group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `js-yaml` from 3.14.1 to 3.14.2
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](https://github.com/nodeca/js-yaml/compare/3.14.1...3.14.2)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Create lazy-snails-return.md (#81)

* Create lazy-snails-return.md
Chores:
Create a new .changeset file to bump the patch version for fnm with a note about fixing the release-to-cargo.yml configuration.
Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/lazy-snails-return.md
Highlights
Changeset Addition: A new changeset file, lazy-snails-return.md, has been added. This file documents a fix related to the release-to-cargo.yml configuration.
Configuration Fix: The changeset entry specifically notes an update to the release-to-cargo.yml configuration, setting its base to br master.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Dargon789 patch 2 (#82)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md

Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/weak-moose-love.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.
Signed-off-by: Dargon789 <[email protected]>

* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update index.mjs (#86)

Code Formatting: Removed an unnecessary blank line in tests/proxy-server/index.mjs to improve code consistency.
Signed-off-by: Dargon789 <[email protected]>

* Create google.yml (#87)

Add a GitHub Actions workflow to build and deploy the application to Google Kubernetes Engine via Google Cloud.
Build:
Introduce a Google Cloud–oriented workflow that builds a Docker image and pushes it to Artifact Registry on pushes to the main branch.
CI:
Add a GitHub Actions pipeline that authenticates with Google Cloud using Workload Identity Federation and runs container build and deployment steps.
Deployment:
Automate deploying the built Docker image to a GKE cluster using kustomize and kubectl.
Signed-off-by: Dargon789 <[email protected]>

* Create ci-hardhat.yml (#89)

Signed-off-by: Dargon789 <[email protected]>

* Create npm.yml (#91)

* Create npm.yml

Signed-off-by: Dargon789 <[email protected]>

* Potential fix for code scanning alert no. 31: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* Update package.json (#93)

* Update package.json

https://github.com/Dargon789/uniswap.app/commit/011f260c7cc540f9bc9b336e0108f10d6f00401f

Signed-off-by: Dargon789 <[email protected]>

* Update package.json

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update README.md (#94)

* Update README.md

Signed-off-by: Dargon789 <[email protected]>

* Update README.md

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update README.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update README.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update README.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update README.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update README.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update README.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Delete .kodiak.toml (#96)

Signed-off-by: Dargon789 <[email protected]>

* Create orb.yml (#97)

https://github.com/Dargon789/circleci-docs/commit/cd854b03e8aa7204da46e1da518ff6d80526a7b3

Signed-off-by: Dargon789 <[email protected]>

* Update Cargo.toml (#98)

* Update Cargo.toml

https://github.com/Dargon789/foundry/commit/fcfa587cbfce70b8eb32ac87207cd8a2e2c4f726

Signed-off-by: Dargon789 <[email protected]>

* Update Cargo.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update label.yml (#99)

CI:

Adjust GitHub Actions label workflow triggers to use the 'main' branch for push events while keeping pull request triggers on 'master'.
Signed-off-by: Dargon789 <[email protected]>

* fix(deps): update all non-major dependencies

* Add build artifacts and fnm.exe to repository

This commit adds the .fnm/fnm.exe binary and various Rust build artifacts under target-wsl/, including .rustc_info.json, CACHEDIR.TAG, and debug fingerprints for dependencies. These files appear to be generated as part of a Rust build process, possibly for debugging or distribution purposes.

* Update issue templates (#102)

* 1462 (#103)

* Adjust install script for POSIX compliance

* Create temporary directory when mktemp is unavailable

* Use "dot" instead of `source` builtin when shell is not fish

* Inform the user where fnm is being installed

* chore(deps): update rust crate indoc to v2.0.7

* Add changeset for updating indoc crate to v2.0.7 (#101)

Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: Ricardo Biehl Pasquali <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

* Update README.md

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update .github/ISSUE_TEMPLATE/bug_report.md

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update .github/ISSUE_TEMPLATE/bug_report.md

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: AU_gdev_19 <[email protected]>
Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: snyk-bot <[email protected]>
Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: Ricardo Biehl Pasquali <[email protected]>

* Add changeset  sixty-rice-do.md for patch 1 (#105)

 sixty-rice-do.md
Signed-off-by: Dargon789 <[email protected]>

* Update Cargo.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update Cargo.toml

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update SECURITY.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update src/hooks.rs

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update test-hooks-integration.sh

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* #1.39.0 (#123)

* Make install.sh tee instead of echoing twice

Also, fish bit was the only one that didn't print a newline to
$CONF_FILE, now they're all the same.

* Check if fnm is installed before shell setup

Change $CONF_FILE append strings to check whether $INSTALL_DIR exists
before doing any setup. This way whenever a user syncs their shell
config across machines, the machines without fnm installed won't throw
errors.

* Create smooth-lions-sneeze.md

* Version Packages

* add hooks mechanism for pre, post and failed install

* feat: upgrade cross-env from 7.0.3 to 10.0.0 (#39)

Snyk has created this PR to upgrade cross-env from 7.0.3 to 10.0.0.

See this package in npm:
cross-env

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* fix: upgrade prettier from 3.5.3 to 3.6.2 (#38)

Snyk has created this PR to upgrade prettier from 3.5.3 to 3.6.2.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* feat: upgrade @types/node from 18.19.123 to 24.1.0 (#36)

Snyk has created this PR to upgrade @types/node from 18.19.123 to 24.1.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* fix: package.json to reduce vulnerabilities (#35)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-TMP-11501554

Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>

* Create label.yml (#40)

* Create label.yml

Signed-off-by: AU_gdev_19 <[email protected]>

* Potential fix for code scanning alert no. 30: Workflow does not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <[email protected]>

---------

Signed-off-by: AU_gdev_19 <[email protected]>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* Update release.yml (#41)

Signed-off-by: AU_gdev_19 <[email protected]>

* chore(deps): bump tracing-subscriber from 0.3.18 to 0.3.20 in the cargo group across 1 directory (#42)

* chore(deps): bump tracing-subscriber

Bumps the cargo group with 1 update in the / directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).


Updates `tracing-subscriber` from 0.3.18 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.18...tracing-subscriber-0.3.20)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>

* Update rust.yml (#43)

Signed-off-by: AU_gdev_19 <[email protected]>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: AU_gdev_19 <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: AU_gdev_19 <[email protected]>

* Adjust install script for POSIX compliance

* Create temporary directory when mktemp is unavailable

* Use "dot" instead of `source` builtin when shell is not fish

* Inform the user where fnm is being installed

* [Snyk] Upgrade @changesets/cli from 2.29.6 to 2.29.7 (#46)

* fix: upgrade @changesets/cli from 2.29.6 to 2.29.7

Snyk has created this PR to upgrade @changesets/cli from 2.29.6 to 2.29.7.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

* Update package.json

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: snyk-bot <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* fix: upgrade cmd-ts from 0.13.0 to 0.14.1 (#45)

Snyk has created this PR to upgrade cmd-ts from 0.13.0 to 0.14.1.

See this package in npm:
cmd-ts

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* feat: upgrade p-retry from 6.2.1 to 7.0.0 (#44)

Snyk has created this PR to upgrade p-retry from 6.2.1 to 7.0.0.

See this package in npm:
p-retry

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <[email protected]>

* chore(deps): bump zip in the cargo group across 1 directory (#47)

Bumps the cargo group with 1 update in the / directory: [zip](https://github.com/zip-rs/zip2).


Updates `zip` from 2.2.0 to 6.0.0
- [Release notes](https://github.com/zip-rs/zip2/releases)
- [Changelog](https://github.com/zip-rs/zip2/blob/master/CHANGELOG.md)
- [Commits](https://github.com/zip-rs/zip2/compare/v2.2.0...v6.0.0)

---
updated-dependencies:
- dependency-name: zip
  dependency-version: 6.0.0
  dependency-type: direct:production
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Create smart-avocados-try.md (#48)

* Create smart-avocados-try.md

Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/smart-avocados-try.md
New Changeset File: A new changeset file, smart-avocados-try.md, has been added to the .changeset directory. This file is used to record a specific change for future release notes or changelog generation.
Patch Metadata: The newly added changeset file includes front matter metadata specifying "fnm": "patch", indicating the type of change being recorded.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update release-to-cargo.yml (#55)

CI:

Modify the Publish to crates.io step to use cargo publish --dry-run
Signed-off-by: Dargon789 <[email protected]>

* Create angry-moose-hug.md (#56)

* Create angry-moose-hug.md

Add a changeset for fnm to patch-release the package and update the release-to-cargo workflow configuration to use the master branch

Bug Fixes:

Update release-to-cargo.yml config to use the master branch
Chores:

Add angry-moose-hug changeset to bump fnm patch version

Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/angry-moose-hug.md

New Changeset File: A new changeset file, "angry-moose-hug.md", has been added to the ".changeset" directory, indicating a recorded change for release management.
Release Configuration Update: The changeset documents a "patch" type change for "fnm", specifically a fix to update the "release-to-cargo.yml" configuration to use "base:br master".

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Create funny-falcons-breathe.md (#57)

* Create funny-falcons-breathe.md
Bug Fixes:

Update release-to-cargo.yml workflow config to use master as the base branch for fnm
Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/funny-falcons-breathe.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update release.yml (#59)

Streamline the release workflow by restricting triggers to master and main branches and pin Node.js to version 22.

CI:

Remove the 'dev' branch from the release workflow triggers
Pin Node.js version to 22 in the release job
Signed-off-by: Dargon789 <[email protected]>

* Create ci.yml (#60)

Add CircleCI pipeline to build, test, and format-check the Rust project with caching for dependencies

CI:

Introduce a CircleCI config (.circleci/ci.yml) using cimg/rust:1.89.0
Run cargo fmt -- --check and cargo test in a single build-and-test job
Cache Cargo dependencies and build artifacts between builds
Signed-off-by: Dargon789 <[email protected]>

* Create ci-say-hello.yml (#61)

CI:

Add .circleci/ci-say-hello.yml with a say-hello job using cimg/base:current and a workflow to run it
Signed-off-by: Dargon789 <[email protected]>

* Create ci-foundry.yml (#62)

Add .circleci/ci-foundry.yml to scaffold a new CircleCI pipeline with a custom Docker executor, a CI job, and a workflow.

CI:

Add initial CircleCI pipeline configuration using version 2.1
Define custom executor with Docker image and Docker Hub credentials
Introduce job 'web3-defi-game-project-' with checkout and placeholder run step
Add workflow 'my-custom-workflow' to orchestrate the CI job
Signed-off-by: Dargon789 <[email protected]>

* Update config.yml (#66)

Restructure the CircleCI configuration by removing the custom executor, adding a sample say-hello job and workflow, and enhancing the file with explanatory comments
CI:
Remove custom executor and replace it with a basic say-hello job using the cimg/base:current Docker image
Introduce a say-hello-workflow to orchestrate the new job
Documentation:

Add inline comments to guide configuration of executors, jobs, steps, and workflows in the CI file
Signed-off-by: Dargon789 <[email protected]>

* Create SECURITY.md (#67)

* Create SECURITY.md

Add a SECURITY.md file to establish the project's security policy, detail supported versions, and outline the vulnerability reporting process.

Documentation:

Introduce SECURITY.md with a security policy and supported versions table
Include guidelines for reporting vulnerabilities and expected response procedures
Signed-off-by: Dargon789 <[email protected]>

* Update SECURITY.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Update SECURITY.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Dargon789 patch 2 (#65)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md

Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/weak-moose-love.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Delete .circleci/ci-say-hello.yml (#69)

CI:
Delete .circleci/ci-say-hello.yml to clean up unused CI pipeline
Signed-off-by: Dargon789 <[email protected]>

* Update ci.yml (#70)

CI:
Use cimg/rust:1.88.0 instead of cimg/rust:1.89.0 in the CI configuration
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the CircleCI configuration to use Rust version 1.88.0, aligning it with the rust-toolchain.toml file. This is a good correction. I have provided one suggestion to use a more flexible image tag to better match the behavior of rustup with the toolchain file, which will improve the long-term maintainability of the CI setup.
Signed-off-by: Dargon789 <[email protected]>

* Update release-to-cargo.yml

Signed-off-by: Dargon789 <[email protected]>

* Update release-to-cargo.yml (#72)

Switch the GitHub Action for releasing to crates.io from a dry run to a real publish and clean up unused permissions settings.
CI:
Remove redundant permissions block from the release-to-cargo workflow
Replace dry-run with actual cargo publish command
Signed-off-by: Dargon789 <[email protected]>

* Update grumpy-dingos-turn.md (#73)

Signed-off-by: Dargon789 <[email protected]>

* Update release.yml (#74)

* Update release.yml

Signed-off-by: Dargon789 <[email protected]>

* Update .github/workflows/release.yml

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>

* Update rust.yml (#75)

CI:
Remove 'dev' branch from rust.yml workflow triggers
Signed-off-by: Dargon789 <[email protected]>

* Create docker.yml (#76)

Add a new GitHub Actions workflow (docker.yml) to automate building, pushing, and signing Docker images via Buildx, metadata extraction, and cosign integration

New Features:

Introduce a Docker CI workflow triggered on schedule, push to master, and semantic version tags, as well as on pull requests
Build and push multi-platform Docker images to GHCR using Buildx with dynamic tagging
Integrate cosign to sign published Docker images using Sigstore identity tokens
Enhancements:

Set up Docker metadata action for tag and label generation
Enable caching strategies for faster builds using GitHub Actions
CI:

Add .github/workflows/docker.yml to define the Docker build and publish pipeline
Chores:

Configure environment variables for registry (GHCR) and image naming based on the repository
Signed-off-by: Dargon789 <[email protected]>

* Create CNAME

* Update rust.yml (#78)

Refine the GitHub Actions rust.yml workflow by restricting triggers to the master branch, pinning Node.js to version 18.x across all setup-node steps, and cleaning up formatting and commented version entries.
CI:

Limit workflow triggers to the master branch only
Pin Node.js setup in all jobs to version 18.x, removing 20.x and 22.x entries
Remove redundant commented Node.js version lines and extra blank lines
Signed-off-by: Dargon789 <[email protected]>

* chore(deps): bump js-yaml in the npm_and_yarn group across 1 directory (#77)

Bumps the npm_and_yarn group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `js-yaml` from 3.14.1 to 3.14.2
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](https://github.com/nodeca/js-yaml/compare/3.14.1...3.14.2)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Create spotty-weeks-sit.md (#80)

Chores:
Create a spotty-weeks-sit changeset specifying a patch release for fnm
Signed-off-by: Dargon789 <[email protected]>

* Create lazy-snails-return.md (#81)

* Create lazy-snails-return.md
Chores:
Create a new .changeset file to bump the patch version for fnm with a note about fixing the release-to-cargo.yml configuration.
Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/lazy-snails-return.md
Highlights
Changeset Addition: A new changeset file, lazy-snails-return.md, has been added. This file documents a fix related to the release-to-cargo.yml configuration.
Configuration Fix: The changeset entry specifically notes an update to the release-to-cargo.yml configuration, setting its base to br master.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Dargon789 patch 2 (#82)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md

Signed-off-by: Dargon789 <[email protected]>

* Update .changeset/weak-moose-love.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.
Signed-off-by: Dargon789 <[email protected]>

* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release
Signed-off-by: Dargon789 <[email protected]>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update index.mjs (#86)

Code Formatting: Removed an unnecessary blank line in tests/proxy-server/index.mjs to improve code consistency.
Signed-off-by: Dargon789 <[email protected]>

* Create google.yml (#87)

Add a GitHub Actions workflow to build and deploy the application to Google Kubernetes Engine via Google Cloud.
Build:
Introduce a Google Cloud–oriented workflow that builds a Docker image and pushes it to Artifact Registry on pushes to the main branch.
CI:
Add a GitHub Actions pipeline that authenticates with Google Cloud using Workload Identity Federation and runs container build and deployment steps.
Deployment:
Automate deploying the built Docker image to a GKE cluster using kustomize and kubectl.
Signed-off-by: Dargon789 <[email protected]>

* Create ci-hardhat.yml (#89)

Signed-off-by: Dargon789 <[email protected]>

* Create npm.yml (#91)

* Create npm.yml

Signed-off-by: Dargon789 <[email protected]>

* Potential fix for code scanning alert no. 31: Artifact poisoning

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <[email protected]>

---------
…
@vercel

This comment was marked as resolved.

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @Dargon789, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Mar 2, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
🔚 Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request delivers a substantial update, rolling up numerous features, dependency upgrades, and infrastructure improvements into version 1.39.0. Key user-facing enhancements include the ability to install the latest Node.js version directly, advanced filtering and sorting for remote versions, and a new --global option for fnm env to manage a single Node.js version across all shell sessions. Under the hood, the PR introduces a safer two-phase symlinking mechanism, refactors core version handling logic, and updates a wide array of Rust and Node.js dependencies. Additionally, the CI/CD pipelines have been substantially expanded and refined, incorporating new workflows for Docker, Google Kubernetes Engine deployment, and general build processes, alongside updated documentation and security policies.

Highlights

  • New fnm install --latest Feature: Users can now install the most recent Node.js version directly using the --latest flag with fnm install.
  • Enhanced Remote Version Listing: The fnm list-remote command now supports advanced filtering and sorting of remote Node.js versions, including options for LTS versions and displaying only the latest matching version.
  • Improved Symlink Management: A robust two-phase symlinking mechanism has been implemented to ensure atomic and safer updates when switching Node.js versions, preventing potential race conditions.
  • Global Node.js Version Support: The fnm env command introduces a new --global flag, allowing users to configure a single global Node.js version that persists across all shell sessions.
  • Extensive Dependency Updates: Numerous Rust and Node.js dependencies have been upgraded, including core libraries like clap, chrono, duct, tar, thiserror, windows-sys, and development tools such as @changesets/cli, @types/node, execa, prettier, and zod.
  • CI/CD Pipeline Refinements: Various GitHub Actions and CircleCI workflows have been introduced or updated to enhance Docker image building, deployment to Google Kubernetes Engine, release management, and general continuous integration tasks.
  • Simplified Version Handling: The internal UserVersion and Version structs have been refactored, removing the SemverRange variant and streamlining version parsing by transitioning from node_semver to the standard semver crate.
Changelog
  • .changeset/fifty-emus-type.md
    • Added a changeset for a minor feature: remote version sorting and filtering.
  • .changeset/moody-fans-shake.md
    • Added a changeset for a patch release: updating non-major Rust dependencies.
  • .changeset/nine-suits-enjoy.md
    • Added a generic changeset for a patch release.
  • .changeset/tame-bobcats-mate.md
    • Added a changeset for a patch feature: support to install the latest version.
  • .changeset/warm-rice-appear.md
    • Added a changeset for a minor feature: support for fnm install --latest.
  • .changeset/wet-donkeys-jump.md
    • Added a changeset for a patch release: updating dev dependencies.
  • Cargo.lock
    • Updated numerous Rust dependency versions and their checksums, including chrono, clap, duct, embed-resource, libc, os_pipe, shared_child, syn, tar, thiserror, windows-link, windows-sys, and windows-targets.
  • Cargo.toml
    • Updated the duct dev-dependency version from 0.13.7 to 1.0.0.
  • docs/commands.md
    • Updated the CLI command documentation to reflect changes in fnm's main command, alias, completions, current, default, env, exec, install, list, list-remote, unalias, uninstall, and use subcommands, including new options and restructured help output.
  • package.json
    • Updated the project version from 1.39.0 to 1.38.1.
    • Changed the repository URL and author.
    • Updated packageManager to [email protected].
    • Updated several dev-dependencies including @changesets/cli, @types/node, cmd-ts, execa, prettier, and which.
  • rust-toolchain.toml
    • Removed chisel-serial and test-groups configurations, simplifying the toolchain definition.
  • site/pnpm-lock.yaml
    • Updated various Node.js package versions and their integrity hashes, including ajv and minimatch.
    • Adjusted dependency references for eslint-plugin-import.
  • src/archive/extract.rs
    • Modified the extract_into trait method to take self by value instead of Box<Self>.
  • src/archive/mod.rs
    • Added conditional compilation attributes (#[cfg(any(unix, debug_assertions))] and #[cfg(any(windows, debug_assertions))]) to the tar and zip modules.
    • Simplified the extract_archive_into method to directly call extract_into.
  • src/archive/tar.rs
    • Modified the extract_into method to take self by value.
    • Added new test cases for tar.gz and tar.xz extraction.
  • src/archive/zip.rs
    • Modified the extract_into method to take self by value.
    • Updated the test case to directly call extract_into without boxing.
  • src/commands/env.rs
    • Added a #[allow(clippy::struct_excessive_bools)] attribute to the Env struct.
    • Introduced a --global flag for global Node.js version management.
    • Updated error handling for symlink creation.
  • src/commands/install.rs
    • Removed Use, HooksManager, ProgressConfig, UserVersionReader imports.
    • Removed progress and use fields from the Install struct.
    • Simplified the apply method by removing hook execution, corepack enabling, and immediate use functionality.
    • Updated error types.
  • src/commands/ls_remote.rs
    • Changed lts argument attribute from expect to allow for clippy.
    • Removed the truncate_except_latest helper function.
    • Added all_versions.sort_by_key(|v| v.version.clone()) before reversing.
    • Updated error type from remote_node_index::Error to crate::http::Error.
  • src/commands/use.rs
    • Replaced replace_symlink with crate::fs::two_phase_symlink for safer symlink operations.
    • Updated the SymlinkingCreationIssue error type.
  • src/config.rs
    • Added a current_global_version_path method to retrieve the path for the global version symlink.
  • src/fs.rs
    • Added a new two_phase_symlink function for atomic symlink creation.
    • Added a TwoPhaseSymlinkError enum for its error handling.
  • src/remote_node_index.rs
    • Removed pretty_serde::DecodeError import and Decode error variant.
    • Simplified the list function to directly deserialize JSON from the HTTP response.
  • src/user_version.rs
    • Removed the SemverRange variant from UserVersion enum.
    • Removed the inferred_alias method.
    • Updated FromStr implementation to use semver::Error.
  • src/version.rs
    • Changed Semver variant to use semver::Version instead of node_semver::Version.
    • Updated parse method to use semver::Error.
    • Adjusted fmt::Display and PartialEq implementations accordingly.
  • test-hooks-integration.sh
    • Modified the build command to (cd "$(dirname "$0")" && cargo build --release) to ensure it runs in the correct directory.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/rust.yml
Activity
  • Initial feature development for installing the latest version and remote version sorting/filtering.
  • Regular chore commits for testing, formatting, and clippy fixes.
  • Numerous dependency updates for both Rust and Node.js packages, often initiated by Snyk.
  • Updates to documentation, including command help and a new SECURITY.md.
  • Refactoring efforts to improve code structure and efficiency, such as using Vec::retain and sort_by_key.
  • CI/CD workflow changes, including setting up CircleCI, updating GitHub Actions for various tasks (release, Docker, npm, labels), and reverting some of these changes.
  • Several .changeset files were created and updated, indicating planned release notes for minor and patch versions.
  • A significant refactor related to fnm env --global and symlink handling.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@Dargon789 Dargon789 merged commit 908db46 into master Mar 2, 2026
8 of 13 checks passed
@Dargon789 Dargon789 deleted the 1.39.0 branch March 2, 2026 00:33
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces several new features and dependency updates while also making significant changes to existing functionality. Key additions include support for fnm install --latest to install the newest Node.js version, and new remote version sorting and filtering capabilities. The fnm env command gains a --global flag for setting a single global Node.js version, utilizing a new two_phase_symlink mechanism for safer symlink updates. Dependency updates are extensive across both Rust (Cargo.lock, Cargo.toml) and JavaScript (package.json, site/pnpm-lock.yaml) packages, including a major duct upgrade and a switch from node-semver to semver in Rust. However, several features have been removed or altered: the install command no longer supports --use or --progress flags, and critically, all pre-install, post-install, and install-failed hooks have been removed. The SemverRange variant has been dropped from UserVersion, removing support for npm-style semver ranges. Documentation for fnm list-remote is incomplete, missing flags like --filter, --lts, --sort, and --latest. Additionally, a logic bug was identified in fnm list-remote where the --latest flag truncates the version list before sorting, potentially returning an arbitrary version instead of the actual latest one.

I am having trouble creating individual review comments. Click here to see my feedback.

src/commands/install.rs (148-181)

critical

The logic for executing pre-install, post-install, and install-failed hooks has been removed from the install command. This is a critical feature regression, especially since the test-hooks-integration.sh script, which tests this functionality, still exists. This suggests the removal might have been accidental. Please restore the hooks functionality.

docs/commands.md (544-592)

high

The documentation for fnm list-remote appears to be incomplete as it's missing important flags like --filter, --lts, --sort, and --latest. These options are still present in the source code, so their absence in the documentation could be misleading for users. Please ensure the generated command documentation is up-to-date and reflects all available options.

src/commands/install.rs (33-41)

high

The --use and --progress flags have been removed from the install command. This is a significant breaking change and a feature regression that might be unexpected for users. If this change was intentional, it should be clearly documented in the release notes.

src/commands/ls_remote.rs (59-66)

high

There appears to be a logic bug when using the --latest flag. The list of versions is truncated to one element before it is sorted. Since the versions from the remote are not guaranteed to be in any specific order, this will likely return an arbitrary version instead of the latest one. The sorting should be performed before any truncation to ensure the correct version is selected.

        all_versions.sort_by_key(|v| v.version.clone());

        if self.latest {
            let len = all_versions.len();
            if len > 1 {
                all_versions.drain(0..len - 1);
            }
        }

        if let SortingMethod::Descending = self.sort {
            all_versions.reverse();
        }

src/user_version.rs (5-9)

high

The SemverRange variant has been removed, and the underlying dependency has been switched from node-semver to semver. This is a significant breaking change as it removes support for npm-style semver ranges (like ^1.2.3, ~1.2.3, etc.) for version matching. This is a feature regression that should be clearly communicated to users in the release notes.

Dargon789 added a commit that referenced this pull request Mar 13, 2026
* feat: support to install the latest version

* chore: test & fmt & clippy

* docs: update command docs

* docs: update command docs

* Create warm-rice-appear.md

* Update change set to be a minor release

As this is a new feature

* chore: update workflow to install pnpm

* Remove `feat:` from changeset

Because GitHub actions approval button is missing

* run pnpm like other tasks

* Revert "run pnpm like other tasks"

This reverts commit f5f2ca2.
we can revert the yarn changes and do it in a different PR

* revert the changes in .github/workflows

* feat: add remote version sorting and filtering

* use `UserVersion` for filtering

* add additional lts filter

* refactor: use `Vec::retain` instead of filtering and collecting

* fix docstring for sort option

* change docstring for filter argument

* refactor vec filtering



* refactor to use `sort_by_key` and `reverse`



* add latest flag

* make filter an option as well

* move sort into command as it is presentational

* fix getting latest version

* refactors

* update docs/commands.md

* sort upon installation

* fix clippy

* don't mention rust structs in the cli docs

* post a token example

* welp

* chore(deps): update actions/setup-node action to v4

* chore(deps): update pnpm to v9

* update devDependencies

* test more stuff in archiving

* fnm env --global: considering if this is a good idea

technically i think that i can just mutate the 'default' alias instead. because now that i think about it,
it makes 0 sense to set current to 'default' every time a new shell is opened. so current _is_ default.

* recovery version corepack

[email protected]

* Circleci project setup (#4)

* Add .circleci/config.yml

* Add .circleci/config.yml

* Add .circleci/config.yml

* Bump ring from 0.17.8 to 0.17.13 in the cargo group across 1 directory (#3)

Bumps the cargo group with 1 update in the / directory: [ring](https://github.com/briansmith/ring).


Updates `ring` from 0.17.8 to 0.17.13
- [Changelog](https://github.com/briansmith/ring/blob/main/RELEASES.md)
- [Commits](https://github.com/briansmith/ring/commits)

---
updated-dependencies:
- dependency-name: ring
  dependency-type: indirect
  dependency-group: cargo
...





* Bump dawidd6/action-download-artifact (#2)

Bumps the github_actions group with 1 update in the /.github/workflows directory: [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact).


Updates `dawidd6/action-download-artifact` from 2 to 6
- [Release notes](https://github.com/dawidd6/action-download-artifact/releases)
- [Commits](dawidd6/action-download-artifact@v2...v6)

---
updated-dependencies:
- dependency-name: dawidd6/action-download-artifact
  dependency-type: direct:production
  dependency-group: github_actions
...





* Create SECURITY.md (#1)



* Revert "Bump dawidd6/action-download-artifact (#2)" (#5)

This reverts commit b454d73.

* Bump tokio from 1.37.0 to 1.42.0 in the cargo group across 1 directory

Bumps the cargo group with 1 update in the / directory: [tokio](https://github.com/tokio-rs/tokio).


Updates `tokio` from 1.37.0 to 1.42.0
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.37.0...tokio-1.42.0)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.42.0
  dependency-type: indirect
  dependency-group: cargo
...



* Bump tokio from 1.42.0 to 1.42.1 in the cargo group across 1 directory (#8)

Bumps the cargo group with 1 update in the / directory: [tokio](https://github.com/tokio-rs/tokio).


Updates `tokio` from 1.42.0 to 1.42.1
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.42.0...tokio-1.42.1)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.42.1
  dependency-type: indirect
  dependency-group: cargo
...




* Bump dawidd6/action-download-artifact (#7)

Bumps the github_actions group with 1 update in the /.github/workflows directory: [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact).


Updates `dawidd6/action-download-artifact` from 2 to 6
- [Release notes](https://github.com/dawidd6/action-download-artifact/releases)
- [Commits](dawidd6/action-download-artifact@v2...v6)

---
updated-dependencies:
- dependency-name: dawidd6/action-download-artifact
  dependency-version: '6'
  dependency-type: direct:production
  dependency-group: github_actions
...





* Create wet-donkeys-jump.md



* feat: upgrade which from 3.0.1 to 5.0.0 (#17)

Snyk has created this PR to upgrade which from 3.0.1 to 5.0.0.

See this package in npm:
which

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade @changesets/cli from 2.27.5 to 2.28.1 (#16)

Snyk has created this PR to upgrade @changesets/cli from 2.27.5 to 2.28.1.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade prettier from 3.3.0 to 3.5.3 (#15)

Snyk has created this PR to upgrade prettier from 3.3.0 to 3.5.3.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade execa from 7.2.0 to 9.5.2 (#14)

Snyk has created this PR to upgrade execa from 7.2.0 to 9.5.2.

See this package in npm:
execa

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade @types/node from 18.19.87 to 22.14.0 (#13)

Snyk has created this PR to upgrade @types/node from 18.19.87 to 22.14.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade @changesets/cli from 2.28.1 to 2.29.1 (#19)

Snyk has created this PR to upgrade @changesets/cli from 2.28.1 to 2.29.1.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade @changesets/cli from 2.29.1 to 2.29.2

Snyk has created this PR to upgrade @changesets/cli from 2.29.1 to 2.29.2.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

* chore(deps): update rust crate embed-resource to v2.5.2

* fix(deps): update rust crate tar to v0.4.44

* fix(deps): update rust crate thiserror to v1.0.69

* chore(deps): update rust crate indoc to v2.0.7

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release


* Add changeset for updating indoc crate to v2.0.7 (#101)



* Update Cargo.toml (#98)  (#104)

* chore(deps): bump the cargo group across 1 directory with 4 updates

Bumps the cargo group with 4 updates in the / directory: [hashbrown](https://github.com/rust-lang/hashbrown), [ring](https://github.com/briansmith/ring), [rustls](https://github.com/rustls/rustls) and [tokio](https://github.com/tokio-rs/tokio).


Updates `hashbrown` from 0.15.0 to 0.15.3
- [Release notes](https://github.com/rust-lang/hashbrown/releases)
- [Changelog](https://github.com/rust-lang/hashbrown/blob/master/CHANGELOG.md)
- [Commits](rust-lang/hashbrown@v0.15.0...v0.15.3)

Updates `ring` from 0.17.8 to 0.17.14
- [Changelog](https://github.com/briansmith/ring/blob/main/RELEASES.md)
- [Commits](https://github.com/briansmith/ring/commits)

Updates `rustls` from 0.23.16 to 0.23.23
- [Release notes](https://github.com/rustls/rustls/releases)
- [Changelog](https://github.com/rustls/rustls/blob/main/CHANGELOG.md)
- [Commits](rustls/rustls@v/0.23.16...v/0.23.23)

Updates `tokio` from 1.41.0 to 1.42.1
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.41.0...tokio-1.42.1)

---
updated-dependencies:
- dependency-name: hashbrown
  dependency-version: 0.15.3
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: ring
  dependency-version: 0.17.14
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: rustls
  dependency-version: 0.23.23
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: tokio
  dependency-version: 1.42.1
  dependency-type: indirect
  dependency-group: cargo
...



* chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates

Bumps the npm_and_yarn group with 2 updates in the / directory: [@babel/helpers](https://github.com/babel/babel/tree/HEAD/packages/babel-helpers) and [@babel/runtime](https://github.com/babel/babel/tree/HEAD/packages/babel-runtime).


Updates `@babel/helpers` from 7.26.0 to 7.27.4
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.27.4/packages/babel-helpers)

Updates `@babel/runtime` from 7.26.0 to 7.27.4
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.27.4/packages/babel-runtime)

---
updated-dependencies:
- dependency-name: "@babel/helpers"
  dependency-version: 7.27.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@babel/runtime"
  dependency-version: 7.27.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
...



* Potential fix for code scanning alert no. 3: Server-side request forgery




* Potential fix for code scanning alert no. 19: Workflow does not contain permissions




* fix: package.json to reduce vulnerabilities (#27)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-INFLIGHT-6095116



* chore(deps): bump brace-expansion

Bumps the npm_and_yarn group with 1 update in the / directory: [brace-expansion](https://github.com/juliangruber/brace-expansion).


Updates `brace-expansion` from 1.1.11 to 1.1.12
- [Release notes](https://github.com/juliangruber/brace-expansion/releases)
- [Commits](juliangruber/brace-expansion@1.1.11...v1.1.12)

---
updated-dependencies:
- dependency-name: brace-expansion
  dependency-version: 1.1.12
  dependency-type: indirect
  dependency-group: npm_and_yarn
...



* Create config.yml (#34)

* feat: upgrade zod from 3.25.76 to 4.0.0 (#33)

Snyk has created this PR to upgrade zod from 3.25.76 to 4.0.0.

See this package in npm:
zod

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade @types/jest from 29.5.14 to 30.0.0 (#32)

Snyk has created this PR to upgrade @types/jest from 29.5.14 to 30.0.0.

See this package in npm:
@types/jest

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade prettier from 3.5.1 to 3.5.3 (#25)

Snyk has created this PR to upgrade prettier from 3.5.1 to 3.5.3.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* feat: upgrade cross-env from 7.0.3 to 10.0.0 (#39)

Snyk has created this PR to upgrade cross-env from 7.0.3 to 10.0.0.

See this package in npm:
cross-env

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* fix: upgrade prettier from 3.5.3 to 3.6.2 (#38)

Snyk has created this PR to upgrade prettier from 3.5.3 to 3.6.2.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* feat: upgrade @types/node from 18.19.123 to 24.1.0 (#36)

Snyk has created this PR to upgrade @types/node from 18.19.123 to 24.1.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* fix: package.json to reduce vulnerabilities (#35)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-TMP-11501554



* Create label.yml (#40)

* Create label.yml



* Potential fix for code scanning alert no. 30: Workflow does not contain permissions




---------




* Update release.yml (#41)



* chore(deps): bump tracing-subscriber from 0.3.18 to 0.3.20 in the cargo group across 1 directory (#42)

* chore(deps): bump tracing-subscriber

Bumps the cargo group with 1 update in the / directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).


Updates `tracing-subscriber` from 0.3.18 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.18...tracing-subscriber-0.3.20)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: indirect
  dependency-group: cargo
...



* Update rust.yml (#43)



---------






* [Snyk] Upgrade @changesets/cli from 2.29.6 to 2.29.7 (#46)

* fix: upgrade @changesets/cli from 2.29.6 to 2.29.7

Snyk has created this PR to upgrade @changesets/cli from 2.29.6 to 2.29.7.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

* Update package.json




---------





* fix: upgrade cmd-ts from 0.13.0 to 0.14.1 (#45)

Snyk has created this PR to upgrade cmd-ts from 0.13.0 to 0.14.1.

See this package in npm:
cmd-ts

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade p-retry from 6.2.1 to 7.0.0 (#44)

Snyk has created this PR to upgrade p-retry from 6.2.1 to 7.0.0.

See this package in npm:
p-retry

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* chore(deps): bump zip in the cargo group across 1 directory (#47)

Bumps the cargo group with 1 update in the / directory: [zip](https://github.com/zip-rs/zip2).


Updates `zip` from 2.2.0 to 6.0.0
- [Release notes](https://github.com/zip-rs/zip2/releases)
- [Changelog](https://github.com/zip-rs/zip2/blob/master/CHANGELOG.md)
- [Commits](zip-rs/zip2@v2.2.0...v6.0.0)

---
updated-dependencies:
- dependency-name: zip
  dependency-version: 6.0.0
  dependency-type: direct:production
  dependency-group: cargo
...




* Update release-to-cargo.yml (#55)

CI:

Modify the Publish to crates.io step to use cargo publish --dry-run


* Create angry-moose-hug.md (#56)

* Create angry-moose-hug.md

Add a changeset for fnm to patch-release the package and update the release-to-cargo workflow configuration to use the master branch

Bug Fixes:

Update release-to-cargo.yml config to use the master branch
Chores:

Add angry-moose-hug changeset to bump fnm patch version



* Update .changeset/angry-moose-hug.md

New Changeset File: A new changeset file, "angry-moose-hug.md", has been added to the ".changeset" directory, indicating a recorded change for release management.
Release Configuration Update: The changeset documents a "patch" type change for "fnm", specifically a fix to update the "release-to-cargo.yml" configuration to use "base:br master".




---------




* Create funny-falcons-breathe.md (#57)

* Create funny-falcons-breathe.md
Bug Fixes:

Update release-to-cargo.yml workflow config to use master as the base branch for fnm


* Update .changeset/funny-falcons-breathe.md




---------




* Update release.yml (#59)

Streamline the release workflow by restricting triggers to master and main branches and pin Node.js to version 22.

CI:

Remove the 'dev' branch from the release workflow triggers
Pin Node.js version to 22 in the release job


* Create ci.yml (#60)

Add CircleCI pipeline to build, test, and format-check the Rust project with caching for dependencies

CI:

Introduce a CircleCI config (.circleci/ci.yml) using cimg/rust:1.89.0
Run cargo fmt -- --check and cargo test in a single build-and-test job
Cache Cargo dependencies and build artifacts between builds


* Create ci-say-hello.yml (#61)

CI:

Add .circleci/ci-say-hello.yml with a say-hello job using cimg/base:current and a workflow to run it


* Create ci-foundry.yml (#62)

Add .circleci/ci-foundry.yml to scaffold a new CircleCI pipeline with a custom Docker executor, a CI job, and a workflow.

CI:

Add initial CircleCI pipeline configuration using version 2.1
Define custom executor with Docker image and Docker Hub credentials
Introduce job 'web3-defi-game-project-' with checkout and placeholder run step
Add workflow 'my-custom-workflow' to orchestrate the CI job


* Update config.yml (#66)

Restructure the CircleCI configuration by removing the custom executor, adding a sample say-hello job and workflow, and enhancing the file with explanatory comments
CI:
Remove custom executor and replace it with a basic say-hello job using the cimg/base:current Docker image
Introduce a say-hello-workflow to orchestrate the new job
Documentation:

Add inline comments to guide configuration of executors, jobs, steps, and workflows in the CI file


* Create SECURITY.md (#67)

* Create SECURITY.md

Add a SECURITY.md file to establish the project's security policy, detail supported versions, and outline the vulnerability reporting process.

Documentation:

Introduce SECURITY.md with a security policy and supported versions table
Include guidelines for reporting vulnerabilities and expected response procedures


* Update SECURITY.md




* Update SECURITY.md




---------




* Dargon789 patch 2 (#65)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


---------





* Delete .circleci/ci-say-hello.yml (#69)

CI:
Delete .circleci/ci-say-hello.yml to clean up unused CI pipeline


* Update ci.yml (#70)

CI:
Use cimg/rust:1.88.0 instead of cimg/rust:1.89.0 in the CI configuration
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the CircleCI configuration to use Rust version 1.88.0, aligning it with the rust-toolchain.toml file. This is a good correction. I have provided one suggestion to use a more flexible image tag to better match the behavior of rustup with the toolchain file, which will improve the long-term maintainability of the CI setup.


* Update release-to-cargo.yml



* Update release-to-cargo.yml (#72)

Switch the GitHub Action for releasing to crates.io from a dry run to a real publish and clean up unused permissions settings.
CI:
Remove redundant permissions block from the release-to-cargo workflow
Replace dry-run with actual cargo publish command


* Update grumpy-dingos-turn.md (#73)



* Update release.yml (#74)

* Update release.yml



* Update .github/workflows/release.yml




---------




* Update rust.yml (#75)

CI:
Remove 'dev' branch from rust.yml workflow triggers


* Create docker.yml (#76)

Add a new GitHub Actions workflow (docker.yml) to automate building, pushing, and signing Docker images via Buildx, metadata extraction, and cosign integration

New Features:

Introduce a Docker CI workflow triggered on schedule, push to master, and semantic version tags, as well as on pull requests
Build and push multi-platform Docker images to GHCR using Buildx with dynamic tagging
Integrate cosign to sign published Docker images using Sigstore identity tokens
Enhancements:

Set up Docker metadata action for tag and label generation
Enable caching strategies for faster builds using GitHub Actions
CI:

Add .github/workflows/docker.yml to define the Docker build and publish pipeline
Chores:

Configure environment variables for registry (GHCR) and image naming based on the repository


* Create CNAME

* Update rust.yml (#78)

Refine the GitHub Actions rust.yml workflow by restricting triggers to the master branch, pinning Node.js to version 18.x across all setup-node steps, and cleaning up formatting and commented version entries.
CI:

Limit workflow triggers to the master branch only
Pin Node.js setup in all jobs to version 18.x, removing 20.x and 22.x entries
Remove redundant commented Node.js version lines and extra blank lines


* chore(deps): bump js-yaml in the npm_and_yarn group across 1 directory (#77)

Bumps the npm_and_yarn group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `js-yaml` from 3.14.1 to 3.14.2
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@3.14.1...3.14.2)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...




* Create lazy-snails-return.md (#81)

* Create lazy-snails-return.md
Chores:
Create a new .changeset file to bump the patch version for fnm with a note about fixing the release-to-cargo.yml configuration.


* Update .changeset/lazy-snails-return.md
Highlights
Changeset Addition: A new changeset file, lazy-snails-return.md, has been added. This file documents a fix related to the release-to-cargo.yml configuration.
Configuration Fix: The changeset entry specifically notes an update to the release-to-cargo.yml configuration, setting its base to br master.



---------




* Dargon789 patch 2 (#82)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release


---------





* Update index.mjs (#86)

Code Formatting: Removed an unnecessary blank line in tests/proxy-server/index.mjs to improve code consistency.


* Create google.yml (#87)

Add a GitHub Actions workflow to build and deploy the application to Google Kubernetes Engine via Google Cloud.
Build:
Introduce a Google Cloud–oriented workflow that builds a Docker image and pushes it to Artifact Registry on pushes to the main branch.
CI:
Add a GitHub Actions pipeline that authenticates with Google Cloud using Workload Identity Federation and runs container build and deployment steps.
Deployment:
Automate deploying the built Docker image to a GKE cluster using kustomize and kubectl.


* Create ci-hardhat.yml (#89)



* Create npm.yml (#91)

* Create npm.yml



* Potential fix for code scanning alert no. 31: Artifact poisoning




---------




* Update package.json (#93)

* Update package.json

Dargon789/uniswap.app@011f260



* Update package.json




---------




* Update README.md (#94)

* Update README.md



* Update README.md




* Update README.md




* Update README.md




* Update README.md




* Update README.md




* Update README.md




* Update README.md




---------





* Delete .kodiak.toml (#96)



* Create orb.yml (#97)

Dargon789/circleci-docs@cd854b0



* Update Cargo.toml (#98)

* Update Cargo.toml

Dargon789/foundry@fcfa587



* Update Cargo.toml




---------




* Update label.yml (#99)

CI:

Adjust GitHub Actions label workflow triggers to use the 'main' branch for push events while keeping pull request triggers on 'master'.


* fix(deps): update all non-major dependencies

* Add build artifacts and fnm.exe to repository

This commit adds the .fnm/fnm.exe binary and various Rust build artifacts under target-wsl/, including .rustc_info.json, CACHEDIR.TAG, and debug fingerprints for dependencies. These files appear to be generated as part of a Rust build process, possibly for debugging or distribution purposes.

* Update issue templates (#102)

* 1462 (#103)

* Adjust install script for POSIX compliance

* Create temporary directory when mktemp is unavailable

* Use "dot" instead of `source` builtin when shell is not fish

* Inform the user where fnm is being installed

* chore(deps): update rust crate indoc to v2.0.7

* Add changeset for updating indoc crate to v2.0.7 (#101)



---------





* Update README.md




* Update .github/ISSUE_TEMPLATE/bug_report.md




* Update .github/ISSUE_TEMPLATE/bug_report.md




---------













* Add changeset  sixty-rice-do.md for patch 1 (#105)

 sixty-rice-do.md


* Update Cargo.toml




* Update Cargo.toml




* Update SECURITY.md




* Update src/hooks.rs




* Update test-hooks-integration.sh




* #1.39.0 (#123)

* Make install.sh tee instead of echoing twice

Also, fish bit was the only one that didn't print a newline to
$CONF_FILE, now they're all the same.

* Check if fnm is installed before shell setup

Change $CONF_FILE append strings to check whether $INSTALL_DIR exists
before doing any setup. This way whenever a user syncs their shell
config across machines, the machines without fnm installed won't throw
errors.

* Create smooth-lions-sneeze.md

* Version Packages

* add hooks mechanism for pre, post and failed install

* feat: upgrade cross-env from 7.0.3 to 10.0.0 (#39)

Snyk has created this PR to upgrade cross-env from 7.0.3 to 10.0.0.

See this package in npm:
cross-env

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* fix: upgrade prettier from 3.5.3 to 3.6.2 (#38)

Snyk has created this PR to upgrade prettier from 3.5.3 to 3.6.2.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* feat: upgrade @types/node from 18.19.123 to 24.1.0 (#36)

Snyk has created this PR to upgrade @types/node from 18.19.123 to 24.1.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* fix: package.json to reduce vulnerabilities (#35)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-TMP-11501554



* Create label.yml (#40)

* Create label.yml



* Potential fix for code scanning alert no. 30: Workflow does not contain permissions




---------




* Update release.yml (#41)



* chore(deps): bump tracing-subscriber from 0.3.18 to 0.3.20 in the cargo group across 1 directory (#42)

* chore(deps): bump tracing-subscriber

Bumps the cargo group with 1 update in the / directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).


Updates `tracing-subscriber` from 0.3.18 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.18...tracing-subscriber-0.3.20)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: indirect
  dependency-group: cargo
...



* Update rust.yml (#43)



---------






* Adjust install script for POSIX compliance

* Create temporary directory when mktemp is unavailable

* Use "dot" instead of `source` builtin when shell is not fish

* Inform the user where fnm is being installed

* [Snyk] Upgrade @changesets/cli from 2.29.6 to 2.29.7 (#46)

* fix: upgrade @changesets/cli from 2.29.6 to 2.29.7

Snyk has created this PR to upgrade @changesets/cli from 2.29.6 to 2.29.7.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

* Update package.json




---------





* fix: upgrade cmd-ts from 0.13.0 to 0.14.1 (#45)

Snyk has created this PR to upgrade cmd-ts from 0.13.0 to 0.14.1.

See this package in npm:
cmd-ts

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade p-retry from 6.2.1 to 7.0.0 (#44)

Snyk has created this PR to upgrade p-retry from 6.2.1 to 7.0.0.

See this package in npm:
p-retry

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* chore(deps): bump zip in the cargo group across 1 directory (#47)

Bumps the cargo group with 1 update in the / directory: [zip](https://github.com/zip-rs/zip2).


Updates `zip` from 2.2.0 to 6.0.0
- [Release notes](https://github.com/zip-rs/zip2/releases)
- [Changelog](https://github.com/zip-rs/zip2/blob/master/CHANGELOG.md)
- [Commits](zip-rs/zip2@v2.2.0...v6.0.0)

---
updated-dependencies:
- dependency-name: zip
  dependency-version: 6.0.0
  dependency-type: direct:production
  dependency-group: cargo
...




* Create smart-avocados-try.md (#48)

* Create smart-avocados-try.md



* Update .changeset/smart-avocados-try.md
New Changeset File: A new changeset file, smart-avocados-try.md, has been added to the .changeset directory. This file is used to record a specific change for future release notes or changelog generation.
Patch Metadata: The newly added changeset file includes front matter metadata specifying "fnm": "patch", indicating the type of change being recorded.



---------




* Update release-to-cargo.yml (#55)

CI:

Modify the Publish to crates.io step to use cargo publish --dry-run


* Create angry-moose-hug.md (#56)

* Create angry-moose-hug.md

Add a changeset for fnm to patch-release the package and update the release-to-cargo workflow configuration to use the master branch

Bug Fixes:

Update release-to-cargo.yml config to use the master branch
Chores:

Add angry-moose-hug changeset to bump fnm patch version



* Update .changeset/angry-moose-hug.md

New Changeset File: A new changeset file, "angry-moose-hug.md", has been added to the ".changeset" directory, indicating a recorded change for release management.
Release Configuration Update: The changeset documents a "patch" type change for "fnm", specifically a fix to update the "release-to-cargo.yml" configuration to use "base:br master".




---------




* Create funny-falcons-breathe.md (#57)

* Create funny-falcons-breathe.md
Bug Fixes:

Update release-to-cargo.yml workflow config to use master as the base branch for fnm


* Update .changeset/funny-falcons-breathe.md




---------




* Update release.yml (#59)

Streamline the release workflow by restricting triggers to master and main branches and pin Node.js to version 22.

CI:

Remove the 'dev' branch from the release workflow triggers
Pin Node.js version to 22 in the release job


* Create ci.yml (#60)

Add CircleCI pipeline to build, test, and format-check the Rust project with caching for dependencies

CI:

Introduce a CircleCI config (.circleci/ci.yml) using cimg/rust:1.89.0
Run cargo fmt -- --check and cargo test in a single build-and-test job
Cache Cargo dependencies and build artifacts between builds


* Create ci-say-hello.yml (#61)

CI:

Add .circleci/ci-say-hello.yml with a say-hello job using cimg/base:current and a workflow to run it


* Create ci-foundry.yml (#62)

Add .circleci/ci-foundry.yml to scaffold a new CircleCI pipeline with a custom Docker executor, a CI job, and a workflow.

CI:

Add initial CircleCI pipeline configuration using version 2.1
Define custom executor with Docker image and Docker Hub credentials
Introduce job 'web3-defi-game-project-' with checkout and placeholder run step
Add workflow 'my-custom-workflow' to orchestrate the CI job


* Update config.yml (#66)

Restructure the CircleCI configuration by removing the custom executor, adding a sample say-hello job and workflow, and enhancing the file with explanatory comments
CI:
Remove custom executor and replace it with a basic say-hello job using the cimg/base:current Docker image
Introduce a say-hello-workflow to orchestrate the new job
Documentation:

Add inline comments to guide configuration of executors, jobs, steps, and workflows in the CI file


* Create SECURITY.md (#67)

* Create SECURITY.md

Add a SECURITY.md file to establish the project's security policy, detail supported versions, and outline the vulnerability reporting process.

Documentation:

Introduce SECURITY.md with a security policy and supported versions table
Include guidelines for reporting vulnerabilities and expected response procedures


* Update SECURITY.md




* Update SECURITY.md




---------




* Dargon789 patch 2 (#65)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


---------





* Delete .circleci/ci-say-hello.yml (#69)

CI:
Delete .circleci/ci-say-hello.yml to clean up unused CI pipeline


* Update ci.yml (#70)

CI:
Use cimg/rust:1.88.0 instead of cimg/rust:1.89.0 in the CI configuration
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the CircleCI configuration to use Rust version 1.88.0, aligning it with the rust-toolchain.toml file. This is a good correction. I have provided one suggestion to use a more flexible image tag to better match the behavior of rustup with the toolchain file, which will improve the long-term maintainability of the CI setup.


* Update release-to-cargo.yml



* Update release-to-cargo.yml (#72)

Switch the GitHub Action for releasing to crates.io from a dry run to a real publish and clean up unused permissions settings.
CI:
Remove redundant permissions block from the release-to-cargo workflow
Replace dry-run with actual cargo publish command


* Update grumpy-dingos-turn.md (#73)



* Update release.yml (#74)

* Update release.yml



* Update .github/workflows/release.yml




---------




* Update rust.yml (#75)

CI:
Remove 'dev' branch from rust.yml workflow triggers


* Create docker.yml (#76)

Add a new GitHub Actions workflow (docker.yml) to automate building, pushing, and signing Docker images via Buildx, metadata extraction, and cosign integration

New Features:

Introduce a Docker CI workflow triggered on schedule, push to master, and semantic version tags, as well as on pull requests
Build and push multi-platform Docker images to GHCR using Buildx with dynamic tagging
Integrate cosign to sign published Docker images using Sigstore identity tokens
Enhancements:

Set up Docker metadata action for tag and label generation
Enable caching strategies for faster builds using GitHub Actions
CI:

Add .github/workflows/docker.yml to define the Docker build and publish pipeline
Chores:

Configure environment variables for registry (GHCR) and image naming based on the repository


* Create CNAME

* Update rust.yml (#78)

Refine the GitHub Actions rust.yml workflow by restricting triggers to the master branch, pinning Node.js to version 18.x across all setup-node steps, and cleaning up formatting and commented version entries.
CI:

Limit workflow triggers to the master branch only
Pin Node.js setup in all jobs to version 18.x, removing 20.x and 22.x entries
Remove redundant commented Node.js version lines and extra blank lines


* chore(deps): bump js-yaml in the npm_and_yarn group across 1 directory (#77)

Bumps the npm_and_yarn group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `js-yaml` from 3.14.1 to 3.14.2
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@3.14.1...3.14.2)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...




* Create spotty-weeks-sit.md (#80)

Chores:
Create a spotty-weeks-sit changeset specifying a patch release for fnm


* Create lazy-snails-return.md (#81)

* Create lazy-snails-return.md
Chores:
Create a new .changeset file to bump the patch version for fnm with a note about fixing the release-to-cargo.yml configuration.


* Update .changeset/lazy-snails-return.md
Highlights
Changeset Addition: A new changeset file, lazy-snails-return.md, has been added. This file documents a fix related to the release-to-cargo.yml configuration.
Configuration Fix: The changeset entry specifically notes an update to the release-to-cargo.yml configuration, setting its base to br master.



---------




* Dargon789 patch 2 (#82)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release


---------





* Update index.mjs (#86)

Code Formatting: Removed an unnecessary blank line in tests/proxy-server/index.mjs to improve code consistency.


* Create google.yml (#87)

Add a GitHub Actions workflow to build and deploy the application to Google Kubernetes Engine via Google Cloud.
Build:
Introduce a Google Cloud–oriented workflow that builds a Docker image and pushes it to Artifact Registry on pushes to the main branch.
CI:
Add a GitHub Actions pipeline that authenticates with Google Cloud using Workload Identity Federation and runs container build and deployment steps.
Deployment:
Automate deploying the built Docker image to a GKE cluster using kustomize and kubectl.


* Create ci-hardhat.yml (#89)



* Create npm.yml (#91)

* Create npm.yml



* Potential fix for code scanning alert no. 31: Artifact poisoning




---------
…

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: AU_gdev_19 <[email protected]>
Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: Fred <[email protected]>
Co-authored-by: Gal Schlezinger <[email protected]>
Co-authored-by: Ryan Cao <[email protected]>
Co-authored-by: Brennan Kinney <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: snyk-bot <[email protected]>
Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: Ricardo Biehl Pasquali <[email protected]>
Co-authored-by: Emilio Vesprini <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Andy Wright <[email protected]>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Dargon789 added a commit that referenced this pull request Mar 13, 2026
* feat: support to install the latest version

* chore: test & fmt & clippy

* docs: update command docs

* docs: update command docs

* Create warm-rice-appear.md

* Update change set to be a minor release

As this is a new feature

* chore: update workflow to install pnpm

* Remove `feat:` from changeset

Because GitHub actions approval button is missing

* run pnpm like other tasks

* Revert "run pnpm like other tasks"

This reverts commit f5f2ca2.
we can revert the yarn changes and do it in a different PR

* revert the changes in .github/workflows

* feat: add remote version sorting and filtering

* use `UserVersion` for filtering

* add additional lts filter

* refactor: use `Vec::retain` instead of filtering and collecting

* fix docstring for sort option

* change docstring for filter argument

* refactor vec filtering



* refactor to use `sort_by_key` and `reverse`



* add latest flag

* make filter an option as well

* move sort into command as it is presentational

* fix getting latest version

* refactors

* update docs/commands.md

* sort upon installation

* fix clippy

* don't mention rust structs in the cli docs

* post a token example

* welp

* chore(deps): update actions/setup-node action to v4

* chore(deps): update pnpm to v9

* update devDependencies

* test more stuff in archiving

* fnm env --global: considering if this is a good idea

technically i think that i can just mutate the 'default' alias instead. because now that i think about it,
it makes 0 sense to set current to 'default' every time a new shell is opened. so current _is_ default.

* recovery version corepack

[email protected]

* Circleci project setup (#4)

* Add .circleci/config.yml

* Add .circleci/config.yml

* Add .circleci/config.yml

* Bump ring from 0.17.8 to 0.17.13 in the cargo group across 1 directory (#3)

Bumps the cargo group with 1 update in the / directory: [ring](https://github.com/briansmith/ring).


Updates `ring` from 0.17.8 to 0.17.13
- [Changelog](https://github.com/briansmith/ring/blob/main/RELEASES.md)
- [Commits](https://github.com/briansmith/ring/commits)

---
updated-dependencies:
- dependency-name: ring
  dependency-type: indirect
  dependency-group: cargo
...





* Bump dawidd6/action-download-artifact (#2)

Bumps the github_actions group with 1 update in the /.github/workflows directory: [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact).


Updates `dawidd6/action-download-artifact` from 2 to 6
- [Release notes](https://github.com/dawidd6/action-download-artifact/releases)
- [Commits](dawidd6/action-download-artifact@v2...v6)

---
updated-dependencies:
- dependency-name: dawidd6/action-download-artifact
  dependency-type: direct:production
  dependency-group: github_actions
...





* Create SECURITY.md (#1)



* Revert "Bump dawidd6/action-download-artifact (#2)" (#5)

This reverts commit b454d73.

* Bump tokio from 1.37.0 to 1.42.0 in the cargo group across 1 directory

Bumps the cargo group with 1 update in the / directory: [tokio](https://github.com/tokio-rs/tokio).


Updates `tokio` from 1.37.0 to 1.42.0
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.37.0...tokio-1.42.0)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.42.0
  dependency-type: indirect
  dependency-group: cargo
...



* Bump tokio from 1.42.0 to 1.42.1 in the cargo group across 1 directory (#8)

Bumps the cargo group with 1 update in the / directory: [tokio](https://github.com/tokio-rs/tokio).


Updates `tokio` from 1.42.0 to 1.42.1
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.42.0...tokio-1.42.1)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.42.1
  dependency-type: indirect
  dependency-group: cargo
...




* Bump dawidd6/action-download-artifact (#7)

Bumps the github_actions group with 1 update in the /.github/workflows directory: [dawidd6/action-download-artifact](https://github.com/dawidd6/action-download-artifact).


Updates `dawidd6/action-download-artifact` from 2 to 6
- [Release notes](https://github.com/dawidd6/action-download-artifact/releases)
- [Commits](dawidd6/action-download-artifact@v2...v6)

---
updated-dependencies:
- dependency-name: dawidd6/action-download-artifact
  dependency-version: '6'
  dependency-type: direct:production
  dependency-group: github_actions
...





* Create wet-donkeys-jump.md



* feat: upgrade which from 3.0.1 to 5.0.0 (#17)

Snyk has created this PR to upgrade which from 3.0.1 to 5.0.0.

See this package in npm:
which

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade @changesets/cli from 2.27.5 to 2.28.1 (#16)

Snyk has created this PR to upgrade @changesets/cli from 2.27.5 to 2.28.1.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade prettier from 3.3.0 to 3.5.3 (#15)

Snyk has created this PR to upgrade prettier from 3.3.0 to 3.5.3.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade execa from 7.2.0 to 9.5.2 (#14)

Snyk has created this PR to upgrade execa from 7.2.0 to 9.5.2.

See this package in npm:
execa

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade @types/node from 18.19.87 to 22.14.0 (#13)

Snyk has created this PR to upgrade @types/node from 18.19.87 to 22.14.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade @changesets/cli from 2.28.1 to 2.29.1 (#19)

Snyk has created this PR to upgrade @changesets/cli from 2.28.1 to 2.29.1.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade @changesets/cli from 2.29.1 to 2.29.2

Snyk has created this PR to upgrade @changesets/cli from 2.29.1 to 2.29.2.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

* chore(deps): update rust crate embed-resource to v2.5.2

* fix(deps): update rust crate tar to v0.4.44

* fix(deps): update rust crate thiserror to v1.0.69

* chore(deps): update rust crate indoc to v2.0.7

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release


* Add changeset for updating indoc crate to v2.0.7 (#101)



* Update Cargo.toml (#98)  (#104)

* chore(deps): bump the cargo group across 1 directory with 4 updates

Bumps the cargo group with 4 updates in the / directory: [hashbrown](https://github.com/rust-lang/hashbrown), [ring](https://github.com/briansmith/ring), [rustls](https://github.com/rustls/rustls) and [tokio](https://github.com/tokio-rs/tokio).


Updates `hashbrown` from 0.15.0 to 0.15.3
- [Release notes](https://github.com/rust-lang/hashbrown/releases)
- [Changelog](https://github.com/rust-lang/hashbrown/blob/master/CHANGELOG.md)
- [Commits](rust-lang/hashbrown@v0.15.0...v0.15.3)

Updates `ring` from 0.17.8 to 0.17.14
- [Changelog](https://github.com/briansmith/ring/blob/main/RELEASES.md)
- [Commits](https://github.com/briansmith/ring/commits)

Updates `rustls` from 0.23.16 to 0.23.23
- [Release notes](https://github.com/rustls/rustls/releases)
- [Changelog](https://github.com/rustls/rustls/blob/main/CHANGELOG.md)
- [Commits](rustls/rustls@v/0.23.16...v/0.23.23)

Updates `tokio` from 1.41.0 to 1.42.1
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.41.0...tokio-1.42.1)

---
updated-dependencies:
- dependency-name: hashbrown
  dependency-version: 0.15.3
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: ring
  dependency-version: 0.17.14
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: rustls
  dependency-version: 0.23.23
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: tokio
  dependency-version: 1.42.1
  dependency-type: indirect
  dependency-group: cargo
...



* chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates

Bumps the npm_and_yarn group with 2 updates in the / directory: [@babel/helpers](https://github.com/babel/babel/tree/HEAD/packages/babel-helpers) and [@babel/runtime](https://github.com/babel/babel/tree/HEAD/packages/babel-runtime).


Updates `@babel/helpers` from 7.26.0 to 7.27.4
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.27.4/packages/babel-helpers)

Updates `@babel/runtime` from 7.26.0 to 7.27.4
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.27.4/packages/babel-runtime)

---
updated-dependencies:
- dependency-name: "@babel/helpers"
  dependency-version: 7.27.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@babel/runtime"
  dependency-version: 7.27.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
...



* Potential fix for code scanning alert no. 3: Server-side request forgery




* Potential fix for code scanning alert no. 19: Workflow does not contain permissions




* fix: package.json to reduce vulnerabilities (#27)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-INFLIGHT-6095116



* chore(deps): bump brace-expansion

Bumps the npm_and_yarn group with 1 update in the / directory: [brace-expansion](https://github.com/juliangruber/brace-expansion).


Updates `brace-expansion` from 1.1.11 to 1.1.12
- [Release notes](https://github.com/juliangruber/brace-expansion/releases)
- [Commits](juliangruber/brace-expansion@1.1.11...v1.1.12)

---
updated-dependencies:
- dependency-name: brace-expansion
  dependency-version: 1.1.12
  dependency-type: indirect
  dependency-group: npm_and_yarn
...



* Create config.yml (#34)

* feat: upgrade zod from 3.25.76 to 4.0.0 (#33)

Snyk has created this PR to upgrade zod from 3.25.76 to 4.0.0.

See this package in npm:
zod

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade @types/jest from 29.5.14 to 30.0.0 (#32)

Snyk has created this PR to upgrade @types/jest from 29.5.14 to 30.0.0.

See this package in npm:
@types/jest

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* fix: upgrade prettier from 3.5.1 to 3.5.3 (#25)

Snyk has created this PR to upgrade prettier from 3.5.1 to 3.5.3.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* feat: upgrade cross-env from 7.0.3 to 10.0.0 (#39)

Snyk has created this PR to upgrade cross-env from 7.0.3 to 10.0.0.

See this package in npm:
cross-env

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* fix: upgrade prettier from 3.5.3 to 3.6.2 (#38)

Snyk has created this PR to upgrade prettier from 3.5.3 to 3.6.2.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* feat: upgrade @types/node from 18.19.123 to 24.1.0 (#36)

Snyk has created this PR to upgrade @types/node from 18.19.123 to 24.1.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* fix: package.json to reduce vulnerabilities (#35)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-TMP-11501554



* Create label.yml (#40)

* Create label.yml



* Potential fix for code scanning alert no. 30: Workflow does not contain permissions




---------




* Update release.yml (#41)



* chore(deps): bump tracing-subscriber from 0.3.18 to 0.3.20 in the cargo group across 1 directory (#42)

* chore(deps): bump tracing-subscriber

Bumps the cargo group with 1 update in the / directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).


Updates `tracing-subscriber` from 0.3.18 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.18...tracing-subscriber-0.3.20)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: indirect
  dependency-group: cargo
...



* Update rust.yml (#43)



---------






* [Snyk] Upgrade @changesets/cli from 2.29.6 to 2.29.7 (#46)

* fix: upgrade @changesets/cli from 2.29.6 to 2.29.7

Snyk has created this PR to upgrade @changesets/cli from 2.29.6 to 2.29.7.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

* Update package.json




---------





* fix: upgrade cmd-ts from 0.13.0 to 0.14.1 (#45)

Snyk has created this PR to upgrade cmd-ts from 0.13.0 to 0.14.1.

See this package in npm:
cmd-ts

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade p-retry from 6.2.1 to 7.0.0 (#44)

Snyk has created this PR to upgrade p-retry from 6.2.1 to 7.0.0.

See this package in npm:
p-retry

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* chore(deps): bump zip in the cargo group across 1 directory (#47)

Bumps the cargo group with 1 update in the / directory: [zip](https://github.com/zip-rs/zip2).


Updates `zip` from 2.2.0 to 6.0.0
- [Release notes](https://github.com/zip-rs/zip2/releases)
- [Changelog](https://github.com/zip-rs/zip2/blob/master/CHANGELOG.md)
- [Commits](zip-rs/zip2@v2.2.0...v6.0.0)

---
updated-dependencies:
- dependency-name: zip
  dependency-version: 6.0.0
  dependency-type: direct:production
  dependency-group: cargo
...




* Update release-to-cargo.yml (#55)

CI:

Modify the Publish to crates.io step to use cargo publish --dry-run


* Create angry-moose-hug.md (#56)

* Create angry-moose-hug.md

Add a changeset for fnm to patch-release the package and update the release-to-cargo workflow configuration to use the master branch

Bug Fixes:

Update release-to-cargo.yml config to use the master branch
Chores:

Add angry-moose-hug changeset to bump fnm patch version



* Update .changeset/angry-moose-hug.md

New Changeset File: A new changeset file, "angry-moose-hug.md", has been added to the ".changeset" directory, indicating a recorded change for release management.
Release Configuration Update: The changeset documents a "patch" type change for "fnm", specifically a fix to update the "release-to-cargo.yml" configuration to use "base:br master".




---------




* Create funny-falcons-breathe.md (#57)

* Create funny-falcons-breathe.md
Bug Fixes:

Update release-to-cargo.yml workflow config to use master as the base branch for fnm


* Update .changeset/funny-falcons-breathe.md




---------




* Update release.yml (#59)

Streamline the release workflow by restricting triggers to master and main branches and pin Node.js to version 22.

CI:

Remove the 'dev' branch from the release workflow triggers
Pin Node.js version to 22 in the release job


* Create ci.yml (#60)

Add CircleCI pipeline to build, test, and format-check the Rust project with caching for dependencies

CI:

Introduce a CircleCI config (.circleci/ci.yml) using cimg/rust:1.89.0
Run cargo fmt -- --check and cargo test in a single build-and-test job
Cache Cargo dependencies and build artifacts between builds


* Create ci-say-hello.yml (#61)

CI:

Add .circleci/ci-say-hello.yml with a say-hello job using cimg/base:current and a workflow to run it


* Create ci-foundry.yml (#62)

Add .circleci/ci-foundry.yml to scaffold a new CircleCI pipeline with a custom Docker executor, a CI job, and a workflow.

CI:

Add initial CircleCI pipeline configuration using version 2.1
Define custom executor with Docker image and Docker Hub credentials
Introduce job 'web3-defi-game-project-' with checkout and placeholder run step
Add workflow 'my-custom-workflow' to orchestrate the CI job


* Update config.yml (#66)

Restructure the CircleCI configuration by removing the custom executor, adding a sample say-hello job and workflow, and enhancing the file with explanatory comments
CI:
Remove custom executor and replace it with a basic say-hello job using the cimg/base:current Docker image
Introduce a say-hello-workflow to orchestrate the new job
Documentation:

Add inline comments to guide configuration of executors, jobs, steps, and workflows in the CI file


* Create SECURITY.md (#67)

* Create SECURITY.md

Add a SECURITY.md file to establish the project's security policy, detail supported versions, and outline the vulnerability reporting process.

Documentation:

Introduce SECURITY.md with a security policy and supported versions table
Include guidelines for reporting vulnerabilities and expected response procedures


* Update SECURITY.md




* Update SECURITY.md




---------




* Dargon789 patch 2 (#65)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


---------





* Delete .circleci/ci-say-hello.yml (#69)

CI:
Delete .circleci/ci-say-hello.yml to clean up unused CI pipeline


* Update ci.yml (#70)

CI:
Use cimg/rust:1.88.0 instead of cimg/rust:1.89.0 in the CI configuration
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the CircleCI configuration to use Rust version 1.88.0, aligning it with the rust-toolchain.toml file. This is a good correction. I have provided one suggestion to use a more flexible image tag to better match the behavior of rustup with the toolchain file, which will improve the long-term maintainability of the CI setup.


* Update release-to-cargo.yml



* Update release-to-cargo.yml (#72)

Switch the GitHub Action for releasing to crates.io from a dry run to a real publish and clean up unused permissions settings.
CI:
Remove redundant permissions block from the release-to-cargo workflow
Replace dry-run with actual cargo publish command


* Update grumpy-dingos-turn.md (#73)



* Update release.yml (#74)

* Update release.yml



* Update .github/workflows/release.yml




---------




* Update rust.yml (#75)

CI:
Remove 'dev' branch from rust.yml workflow triggers


* Create docker.yml (#76)

Add a new GitHub Actions workflow (docker.yml) to automate building, pushing, and signing Docker images via Buildx, metadata extraction, and cosign integration

New Features:

Introduce a Docker CI workflow triggered on schedule, push to master, and semantic version tags, as well as on pull requests
Build and push multi-platform Docker images to GHCR using Buildx with dynamic tagging
Integrate cosign to sign published Docker images using Sigstore identity tokens
Enhancements:

Set up Docker metadata action for tag and label generation
Enable caching strategies for faster builds using GitHub Actions
CI:

Add .github/workflows/docker.yml to define the Docker build and publish pipeline
Chores:

Configure environment variables for registry (GHCR) and image naming based on the repository


* Create CNAME

* Update rust.yml (#78)

Refine the GitHub Actions rust.yml workflow by restricting triggers to the master branch, pinning Node.js to version 18.x across all setup-node steps, and cleaning up formatting and commented version entries.
CI:

Limit workflow triggers to the master branch only
Pin Node.js setup in all jobs to version 18.x, removing 20.x and 22.x entries
Remove redundant commented Node.js version lines and extra blank lines


* chore(deps): bump js-yaml in the npm_and_yarn group across 1 directory (#77)

Bumps the npm_and_yarn group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `js-yaml` from 3.14.1 to 3.14.2
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@3.14.1...3.14.2)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...




* Create lazy-snails-return.md (#81)

* Create lazy-snails-return.md
Chores:
Create a new .changeset file to bump the patch version for fnm with a note about fixing the release-to-cargo.yml configuration.


* Update .changeset/lazy-snails-return.md
Highlights
Changeset Addition: A new changeset file, lazy-snails-return.md, has been added. This file documents a fix related to the release-to-cargo.yml configuration.
Configuration Fix: The changeset entry specifically notes an update to the release-to-cargo.yml configuration, setting its base to br master.



---------




* Dargon789 patch 2 (#82)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release


---------





* Update index.mjs (#86)

Code Formatting: Removed an unnecessary blank line in tests/proxy-server/index.mjs to improve code consistency.


* Create google.yml (#87)

Add a GitHub Actions workflow to build and deploy the application to Google Kubernetes Engine via Google Cloud.
Build:
Introduce a Google Cloud–oriented workflow that builds a Docker image and pushes it to Artifact Registry on pushes to the main branch.
CI:
Add a GitHub Actions pipeline that authenticates with Google Cloud using Workload Identity Federation and runs container build and deployment steps.
Deployment:
Automate deploying the built Docker image to a GKE cluster using kustomize and kubectl.


* Create ci-hardhat.yml (#89)



* Create npm.yml (#91)

* Create npm.yml



* Potential fix for code scanning alert no. 31: Artifact poisoning




---------




* Update package.json (#93)

* Update package.json

Dargon789/uniswap.app@011f260



* Update package.json




---------




* Update README.md (#94)

* Update README.md



* Update README.md




* Update README.md




* Update README.md




* Update README.md




* Update README.md




* Update README.md




* Update README.md




---------





* Delete .kodiak.toml (#96)



* Create orb.yml (#97)

Dargon789/circleci-docs@cd854b0



* Update Cargo.toml (#98)

* Update Cargo.toml

Dargon789/foundry@fcfa587



* Update Cargo.toml




---------




* Update label.yml (#99)

CI:

Adjust GitHub Actions label workflow triggers to use the 'main' branch for push events while keeping pull request triggers on 'master'.


* fix(deps): update all non-major dependencies

* Add build artifacts and fnm.exe to repository

This commit adds the .fnm/fnm.exe binary and various Rust build artifacts under target-wsl/, including .rustc_info.json, CACHEDIR.TAG, and debug fingerprints for dependencies. These files appear to be generated as part of a Rust build process, possibly for debugging or distribution purposes.

* Update issue templates (#102)

* 1462 (#103)

* Adjust install script for POSIX compliance

* Create temporary directory when mktemp is unavailable

* Use "dot" instead of `source` builtin when shell is not fish

* Inform the user where fnm is being installed

* chore(deps): update rust crate indoc to v2.0.7

* Add changeset for updating indoc crate to v2.0.7 (#101)



---------





* Update README.md




* Update .github/ISSUE_TEMPLATE/bug_report.md




* Update .github/ISSUE_TEMPLATE/bug_report.md




---------













* Add changeset  sixty-rice-do.md for patch 1 (#105)

 sixty-rice-do.md


* Update Cargo.toml




* Update Cargo.toml




* Update SECURITY.md




* Update src/hooks.rs




* Update test-hooks-integration.sh




* #1.39.0 (#123)

* Make install.sh tee instead of echoing twice

Also, fish bit was the only one that didn't print a newline to
$CONF_FILE, now they're all the same.

* Check if fnm is installed before shell setup

Change $CONF_FILE append strings to check whether $INSTALL_DIR exists
before doing any setup. This way whenever a user syncs their shell
config across machines, the machines without fnm installed won't throw
errors.

* Create smooth-lions-sneeze.md

* Version Packages

* add hooks mechanism for pre, post and failed install

* feat: upgrade cross-env from 7.0.3 to 10.0.0 (#39)

Snyk has created this PR to upgrade cross-env from 7.0.3 to 10.0.0.

See this package in npm:
cross-env

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* fix: upgrade prettier from 3.5.3 to 3.6.2 (#38)

Snyk has created this PR to upgrade prettier from 3.5.3 to 3.6.2.

See this package in npm:
prettier

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* feat: upgrade @types/node from 18.19.123 to 24.1.0 (#36)

Snyk has created this PR to upgrade @types/node from 18.19.123 to 24.1.0.

See this package in npm:
@types/node

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/ad4c7706-9351-484f-a545-90686691e99c?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr



* fix: package.json to reduce vulnerabilities (#35)

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-TMP-11501554



* Create label.yml (#40)

* Create label.yml



* Potential fix for code scanning alert no. 30: Workflow does not contain permissions




---------




* Update release.yml (#41)



* chore(deps): bump tracing-subscriber from 0.3.18 to 0.3.20 in the cargo group across 1 directory (#42)

* chore(deps): bump tracing-subscriber

Bumps the cargo group with 1 update in the / directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).


Updates `tracing-subscriber` from 0.3.18 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.18...tracing-subscriber-0.3.20)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: indirect
  dependency-group: cargo
...



* Update rust.yml (#43)



---------






* Adjust install script for POSIX compliance

* Create temporary directory when mktemp is unavailable

* Use "dot" instead of `source` builtin when shell is not fish

* Inform the user where fnm is being installed

* [Snyk] Upgrade @changesets/cli from 2.29.6 to 2.29.7 (#46)

* fix: upgrade @changesets/cli from 2.29.6 to 2.29.7

Snyk has created this PR to upgrade @changesets/cli from 2.29.6 to 2.29.7.

See this package in npm:
@changesets/cli

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr

* Update package.json




---------





* fix: upgrade cmd-ts from 0.13.0 to 0.14.1 (#45)

Snyk has created this PR to upgrade cmd-ts from 0.13.0 to 0.14.1.

See this package in npm:
cmd-ts

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* feat: upgrade p-retry from 6.2.1 to 7.0.0 (#44)

Snyk has created this PR to upgrade p-retry from 6.2.1 to 7.0.0.

See this package in npm:
p-retry

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d81b0d0c-fd3c-4e68-ba3e-6a804eb0d25e?utm_source=github&utm_medium=referral&page=upgrade-pr



* chore(deps): bump zip in the cargo group across 1 directory (#47)

Bumps the cargo group with 1 update in the / directory: [zip](https://github.com/zip-rs/zip2).


Updates `zip` from 2.2.0 to 6.0.0
- [Release notes](https://github.com/zip-rs/zip2/releases)
- [Changelog](https://github.com/zip-rs/zip2/blob/master/CHANGELOG.md)
- [Commits](zip-rs/zip2@v2.2.0...v6.0.0)

---
updated-dependencies:
- dependency-name: zip
  dependency-version: 6.0.0
  dependency-type: direct:production
  dependency-group: cargo
...




* Create smart-avocados-try.md (#48)

* Create smart-avocados-try.md



* Update .changeset/smart-avocados-try.md
New Changeset File: A new changeset file, smart-avocados-try.md, has been added to the .changeset directory. This file is used to record a specific change for future release notes or changelog generation.
Patch Metadata: The newly added changeset file includes front matter metadata specifying "fnm": "patch", indicating the type of change being recorded.



---------




* Update release-to-cargo.yml (#55)

CI:

Modify the Publish to crates.io step to use cargo publish --dry-run


* Create angry-moose-hug.md (#56)

* Create angry-moose-hug.md

Add a changeset for fnm to patch-release the package and update the release-to-cargo workflow configuration to use the master branch

Bug Fixes:

Update release-to-cargo.yml config to use the master branch
Chores:

Add angry-moose-hug changeset to bump fnm patch version



* Update .changeset/angry-moose-hug.md

New Changeset File: A new changeset file, "angry-moose-hug.md", has been added to the ".changeset" directory, indicating a recorded change for release management.
Release Configuration Update: The changeset documents a "patch" type change for "fnm", specifically a fix to update the "release-to-cargo.yml" configuration to use "base:br master".




---------




* Create funny-falcons-breathe.md (#57)

* Create funny-falcons-breathe.md
Bug Fixes:

Update release-to-cargo.yml workflow config to use master as the base branch for fnm


* Update .changeset/funny-falcons-breathe.md




---------




* Update release.yml (#59)

Streamline the release workflow by restricting triggers to master and main branches and pin Node.js to version 22.

CI:

Remove the 'dev' branch from the release workflow triggers
Pin Node.js version to 22 in the release job


* Create ci.yml (#60)

Add CircleCI pipeline to build, test, and format-check the Rust project with caching for dependencies

CI:

Introduce a CircleCI config (.circleci/ci.yml) using cimg/rust:1.89.0
Run cargo fmt -- --check and cargo test in a single build-and-test job
Cache Cargo dependencies and build artifacts between builds


* Create ci-say-hello.yml (#61)

CI:

Add .circleci/ci-say-hello.yml with a say-hello job using cimg/base:current and a workflow to run it


* Create ci-foundry.yml (#62)

Add .circleci/ci-foundry.yml to scaffold a new CircleCI pipeline with a custom Docker executor, a CI job, and a workflow.

CI:

Add initial CircleCI pipeline configuration using version 2.1
Define custom executor with Docker image and Docker Hub credentials
Introduce job 'web3-defi-game-project-' with checkout and placeholder run step
Add workflow 'my-custom-workflow' to orchestrate the CI job


* Update config.yml (#66)

Restructure the CircleCI configuration by removing the custom executor, adding a sample say-hello job and workflow, and enhancing the file with explanatory comments
CI:
Remove custom executor and replace it with a basic say-hello job using the cimg/base:current Docker image
Introduce a say-hello-workflow to orchestrate the new job
Documentation:

Add inline comments to guide configuration of executors, jobs, steps, and workflows in the CI file


* Create SECURITY.md (#67)

* Create SECURITY.md

Add a SECURITY.md file to establish the project's security policy, detail supported versions, and outline the vulnerability reporting process.

Documentation:

Introduce SECURITY.md with a security policy and supported versions table
Include guidelines for reporting vulnerabilities and expected response procedures


* Update SECURITY.md




* Update SECURITY.md




---------




* Dargon789 patch 2 (#65)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


---------





* Delete .circleci/ci-say-hello.yml (#69)

CI:
Delete .circleci/ci-say-hello.yml to clean up unused CI pipeline


* Update ci.yml (#70)

CI:
Use cimg/rust:1.88.0 instead of cimg/rust:1.89.0 in the CI configuration
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the CircleCI configuration to use Rust version 1.88.0, aligning it with the rust-toolchain.toml file. This is a good correction. I have provided one suggestion to use a more flexible image tag to better match the behavior of rustup with the toolchain file, which will improve the long-term maintainability of the CI setup.


* Update release-to-cargo.yml



* Update release-to-cargo.yml (#72)

Switch the GitHub Action for releasing to crates.io from a dry run to a real publish and clean up unused permissions settings.
CI:
Remove redundant permissions block from the release-to-cargo workflow
Replace dry-run with actual cargo publish command


* Update grumpy-dingos-turn.md (#73)



* Update release.yml (#74)

* Update release.yml



* Update .github/workflows/release.yml




---------




* Update rust.yml (#75)

CI:
Remove 'dev' branch from rust.yml workflow triggers


* Create docker.yml (#76)

Add a new GitHub Actions workflow (docker.yml) to automate building, pushing, and signing Docker images via Buildx, metadata extraction, and cosign integration

New Features:

Introduce a Docker CI workflow triggered on schedule, push to master, and semantic version tags, as well as on pull requests
Build and push multi-platform Docker images to GHCR using Buildx with dynamic tagging
Integrate cosign to sign published Docker images using Sigstore identity tokens
Enhancements:

Set up Docker metadata action for tag and label generation
Enable caching strategies for faster builds using GitHub Actions
CI:

Add .github/workflows/docker.yml to define the Docker build and publish pipeline
Chores:

Configure environment variables for registry (GHCR) and image naming based on the repository


* Create CNAME

* Update rust.yml (#78)

Refine the GitHub Actions rust.yml workflow by restricting triggers to the master branch, pinning Node.js to version 18.x across all setup-node steps, and cleaning up formatting and commented version entries.
CI:

Limit workflow triggers to the master branch only
Pin Node.js setup in all jobs to version 18.x, removing 20.x and 22.x entries
Remove redundant commented Node.js version lines and extra blank lines


* chore(deps): bump js-yaml in the npm_and_yarn group across 1 directory (#77)

Bumps the npm_and_yarn group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `js-yaml` from 3.14.1 to 3.14.2
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@3.14.1...3.14.2)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...




* Create spotty-weeks-sit.md (#80)

Chores:
Create a spotty-weeks-sit changeset specifying a patch release for fnm


* Create lazy-snails-return.md (#81)

* Create lazy-snails-return.md
Chores:
Create a new .changeset file to bump the patch version for fnm with a note about fixing the release-to-cargo.yml configuration.


* Update .changeset/lazy-snails-return.md
Highlights
Changeset Addition: A new changeset file, lazy-snails-return.md, has been added. This file documents a fix related to the release-to-cargo.yml configuration.
Configuration Fix: The changeset entry specifically notes an update to the release-to-cargo.yml configuration, setting its base to br master.



---------




* Dargon789 patch 2 (#82)

* chore(deps): update actions/setup-node action to v4

* Create weak-moose-love.md



* Update .changeset/weak-moose-love.md




* Create config.yml (#64)

CI:
Introduce .circleci/config.yml defining a 'say-hello' job and corresponding workflow

https://github.com/apps/gemini-code-assist
Highlights
New CircleCI Configuration: A new .circleci/config.yml file has been added to the repository, establishing a continuous integration setup.
Basic 'Hello, World!' Job: The initial configuration includes a simple job named say-hello that uses the cimg/base:current Docker image to print 'Hello, World!'.
Workflow Definition: A workflow named say-hello-workflow has been defined to orchestrate and run the say-hello job.
Code Review
This pull request introduces a basic CircleCI configuration file. The initial setup is a good starting point. I have provided a couple of suggestions to improve it for better maintainability and reproducibility. My main feedback is to pin the Docker image version to a specific tag instead of using current to ensure consistent builds. I've also pointed out a minor formatting issue with a trailing empty line.


* Create olive-waves-punch.md (#79)

Chores:
Add a new changeset file for fnm patch release


---------





* Update index.mjs (#86)

Code Formatting: Removed an unnecessary blank line in tests/proxy-server/index.mjs to improve code consistency.


* Create google.yml (#87)

Add a GitHub Actions workflow to build and deploy the application to Google Kubernetes Engine via Google Cloud.
Build:
Introduce a Google Cloud–oriented workflow that builds a Docker image and pushes it to Artifact Registry on pushes to the main branch.
CI:
Add a GitHub Actions pipeline that authenticates with Google Cloud using Workload Identity Federation and runs container build and deployment steps.
Deployment:
Automate deploying the built Docker image to a GKE cluster using kustomize and kubectl.


* Create ci-hardhat.yml (#89)



* Create npm.yml (#91)

* Create npm.yml



* Potential fix for code scanning alert no. 31: Artifact poisoning




---------
…

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: AU_gdev_19 <[email protected]>
Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: Fred <[email protected]>
Co-authored-by: Gal Schlezinger <[email protected]>
Co-authored-by: Ryan Cao <[email protected]>
Co-authored-by: Brennan Kinney <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: snyk-bot <[email protected]>
Co-authored-by: snyk-io[bot] <141718529+snyk-io[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: Ricardo Biehl Pasquali <[email protected]>
Co-authored-by: Emilio Vesprini <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Andy Wright <[email protected]>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant