Skip to content

Revert 118 revert 115 dargon789 patch 9#208

Open
Dargon789 wants to merge 247 commits into
Schniz-fnmfrom
revert-118-revert-115-Dargon789-patch-9
Open

Revert 118 revert 115 dargon789 patch 9#208
Dargon789 wants to merge 247 commits into
Schniz-fnmfrom
revert-118-revert-115-Dargon789-patch-9

Conversation

@Dargon789
Copy link
Copy Markdown
Owner

No description provided.

nzhl and others added 30 commits November 18, 2022 01:11
Because GitHub actions approval button is missing
This reverts commit f5f2ca2.
we can revert the yarn changes and do it in a different PR
Also, fish bit was the only one that didn't print a newline to
$CONF_FILE, now they're all the same.
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.
Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>
Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>
Dargon789 and others added 23 commits March 2, 2026 05:28
* 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

Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>

* refactor to use `sort_by_key` and `reverse`

Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>

* 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

* 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.

* 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 clap-rs

* chore(deps): update rust crate chrono to v0.4.44

* chore(deps): update all dev dependencies

---------

Co-authored-by: Fred <nzhlfred@gmail.com>
Co-authored-by: Gal Schlezinger <gal@spitfire.co.il>
Co-authored-by: Ryan Cao <70191398+ryanccn@users.noreply.github.com>
Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…dates (#146)

Bumps the npm_and_yarn group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@babel/helpers](https://github.com/babel/babel/tree/HEAD/packages/babel-helpers) | `7.26.0` | `7.28.6` |
| [brace-expansion](https://github.com/juliangruber/brace-expansion) | `1.1.11` | `1.1.12` |
| [js-yaml](https://github.com/nodeca/js-yaml) | `3.14.1` | `3.14.2` |
| [lodash](https://github.com/lodash/lodash) | `4.17.21` | `4.17.23` |
| [minimatch](https://github.com/isaacs/minimatch) | `3.1.2` | `3.1.5` |



Updates `@babel/helpers` from 7.26.0 to 7.28.6
- [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.28.6/packages/babel-helpers)

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)

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)

Updates `lodash` from 4.17.21 to 4.17.23
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.21...4.17.23)

Updates `minimatch` from 3.1.2 to 3.1.5
- [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md)
- [Commits](isaacs/minimatch@v3.1.2...v3.1.5)

---
updated-dependencies:
- dependency-name: "@babel/helpers"
  dependency-version: 7.28.6
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: brace-expansion
  dependency-version: 1.1.12
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: lodash
  dependency-version: 4.17.23
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: minimatch
  dependency-version: 3.1.5
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* 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

pnpm@8.15.8

* 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] <support@github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Fred <nzhlfred@gmail.com>
Co-authored-by: Gal Schlezinger <gal@spitfire.co.il>
Co-authored-by: Ryan Cao <70191398+ryanccn@users.noreply.github.com>
Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>
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 <snyk-bot@snyk.io>
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 <ricardo@pasqua.li>
Co-authored-by: Emilio Vesprini <emivespa1@gmail.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Andy Wright <atwright147@gmail.com>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
* chore(deps): update dawidd6/action-download-artifact action to v3

* Create smart-ladybugs-punch.md (#135)

* Create smart-ladybugs-punch.md
Chores:

Record a patch-level fnm changeset describing the Renovate upgrade of dawidd6/action-download-artifact to the 3.x series.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update .changeset/smart-ladybugs-punch.md

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

---------

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

* Create itchy-rice-beg.md

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

---------

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
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>
Snyk has created this PR to upgrade @changesets/changelog-github from 0.5.0 to 0.5.1.

See this package in npm:
@changesets/changelog-github

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>
863f4db

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* 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

pnpm@8.15.8

* 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




* Version Packages (#114)



* Remove 'main' branch from release workflow triggers (#115)



* Revert "Remove 'main' branch from release workflow triggers (#115)" (#118)

This reverts commit 21b6cc1.

* Update src/hooks.rs




* Update test-hooks-integration.sh




* Update test-hooks-integration.sh




* Changeset release/master v1.39.0 (#125)

* 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 deployme…

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Fred <nzhlfred@gmail.com>
Co-authored-by: Gal Schlezinger <gal@spitfire.co.il>
Co-authored-by: Ryan Cao <70191398+ryanccn@users.noreply.github.com>
Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>
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 <snyk-bot@snyk.io>
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 <ricardo@pasqua.li>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Emilio Vesprini <emivespa1@gmail.com>
Co-authored-by: Andy Wright <atwright147@gmail.com>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
* Create honest-suns-fetch.md

Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>

* Update .changeset/honest-suns-fetch.md

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

---------

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

Expand the Node.js versions configured in the release workflow's setup-node step.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
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, your pull request is larger than the review limit of 150000 diff characters

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Apr 5, 2026

Snyk checks have failed. 5 issues have been found so far.

Status Scan Engine Critical High Medium Low Total (5)
Open Source Security 0 0 4 1 5 issues

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

@mergify
Copy link
Copy Markdown

mergify Bot commented Apr 5, 2026

⚠️ The sha of the head commit of this PR conflicts with #170. Mergify cannot evaluate rules on this PR. Once #170 is merged or closed, Mergify will resume processing this PR. ⚠️

@Dargon789 Dargon789 enabled auto-merge (rebase) April 5, 2026 14:40
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 updates fnm to version 1.39.0, introducing a new hooks system for installation events, a global version management option via the env --global flag, and a Next.js-based project website. The changes include migrating to the semver crate, implementing atomic symlink updates with a two-phase approach, and refactoring remote version listing and archive extraction logic, alongside an update to the project's authorship and repository metadata. Feedback indicates that placeholder summaries in changeset files should be replaced with descriptive text, redundant steps in the CircleCI configuration should be removed, and a duplicate field in the bug report template needs to be deleted.

Comment thread .changeset/nine-suits-enjoy.md
Comment thread .circleci/ci.yml
Comment thread .github/ISSUE_TEMPLATE/bug_report.md
@Dargon789 Dargon789 linked an issue Apr 15, 2026 that may be closed by this pull request
@mergify
Copy link
Copy Markdown

mergify Bot commented May 23, 2026

⚠️ The sha of the head commit of this PR conflicts with #170. Mergify cannot evaluate rules on this PR. Once #170 is merged or closed, Mergify will resume processing this PR. ⚠️

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.

Sequence diagram for fnm env --use-on-cd eager initial use

7 participants