chore(deps): bump docker/metadata-action from 5 to 6#566
Closed
dependabot[bot] wants to merge 10 commits into
Closed
chore(deps): bump docker/metadata-action from 5 to 6#566dependabot[bot] wants to merge 10 commits into
dependabot[bot] wants to merge 10 commits into
Conversation
* Update CircleCI config with comments and formatting
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update config.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update and rename ci-say-hello.yml to ci-web3-defi-gamefi.yml (#154)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/ci-web3-defi-gamefi.yml (#155)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/ci_deploy.yml (#158)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/cargo.yml (#159)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* chore(deps): bump taiki-e/install-action from 2.62.31 to 2.62.33 (#162)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.62.31 to 2.62.33.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/0005e0116e92d8489d8d96fbff83f061c79ba95a...e43a5023a747770bfcb71ae048541a681714b951)
---
updated-dependencies:
- dependency-name: taiki-e/install-action
dependency-version: 2.62.33
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* chore(deps): bump actions/checkout from 4 to 5 (#163)
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v4...v5)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: '5'
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Merge branch 'foundry-rs:master' (#164)
* Create ci_cargo.yml (#72)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Create config.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Rename ci_cargo.yml to cargo.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* fix(fmt): handle trailing coments between base contracts (#12127)
* fix(fmt): account for ternary operators when estimating size
* fix(fmt): handle comments between inherited base contracts
* test: layout + base inheritance
* feat(forge): add bypass prevrandao (#12125)
* feat(forge): add bypass prevrandao
* Update crates/evm/networks/src/lib.rs
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
* changes after review: remove duped code
---------
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
* fix(fmt): filter libs when recursing (#12119)
* fix(fmt): account for ternary operators when estimating size
* fix(fmt): filter libs when recursing
* style: clippy
* test: wipe contracts before formatting
* test: explicitly test ignore
* fix(fmt): break try stmts in a fn header-like fashion (#12131)
* chore(deps): bump softprops/action-gh-release from 2.3.4 to 2.4.1
Bumps [softprops/action-gh-release](https://github.com/softprops/action-gh-release) from 2.3.4 to 2.4.1.
- [Release notes](https://github.com/softprops/action-gh-release/releases)
- [Changelog](https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md)
- [Commits](https://github.com/softprops/action-gh-release/compare/62c96d0c4e8a889135c1f3a25910db8dbe0e85f7...6da8fa9354ddfdc4aeace5fc48d7f679b5214090)
---
updated-dependencies:
- dependency-name: softprops/action-gh-release
dependency-version: 2.4.1
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
* chore(deps): bump taiki-e/install-action from 2.62.28 to 2.62.33 (#161)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.62.28 to 2.62.33.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/e7ef886cf8f69c25ecef6bbc2858a42e273496ec...e43a5023a747770bfcb71ae048541a681714b951)
---
updated-dependencies:
- dependency-name: taiki-e/install-action
dependency-version: 2.62.33
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---------
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix(anvil): always disable nonce check (foundry-rs#12144) (#165)
* test: refactor testdata/ tests to be run in `forge test` (#12049)
* test: run forge test on testdata/
* chore: refactor to use common Test contract
* chore: disable testGasMeteringExternal, via-ir
* test: rm unused repros
* fix: paths
* upd
* fmt
* fix more tests
* test: turn testNonExistingContractRevert into expectRevert
* fix some more paths
* legacy assertions
* compile paris with paris
* fix: set configs for fs tests
* fix remaining paths in cheats
* restrict fs permissions
* fix: set runtime evm_version too
* fix vyper
* fix: a couple of repros
* fix: we have storage layouts
* fix: 3223, 3674: set sender
* reorder
* feat: move repros expected failures to snapshots
* feat: migrate remaining repros tests
* feat: rm migrated files
* skip testRevertIfGetUnlinked
* move expected core/ failures
* upd
* move logs/
* move all forgetest tests from it/ to cli/
* fix fork test
* move trace/
* tmp: move fuzz/invariant out of fuzz/
* move fuzz/
* forge fmt
* wips
* fix: both vyper and paris; set src/
* canon
* lib log
* logs
* Revert "fix: set runtime evm_version too"
This reverts commit 7ca544b10047f608d57c74fb3500a5fbe7e2650e.
Contract-level inline config will set evm version for libraries too,
which means we fail on deploying libraries that are compiled with
newer evm version.
* fix: set evm version where needed, per test function
* test: reduce gas wastage
* chore: clippy
* invariant mod.rs
* test: fix linking tests with new utils
* redact_with
* Revert "wips"
This reverts commit ee2c17a3023ca7ce8e7effccf0ea0a0f28f6e510.
* migrate invariant/target{,Abi}
* migrate InvariantAfterInvariant.t.sol
* migrate InvariantAssume.t.sol
* migrate InvariantCalldataDictionary.t.sol, more test utils
* migrate InvariantCustomError.t.sol
* migrate InvariantExcludedSenders.t.sol
* migrate InvariantFixtures.t.sol
* migrate InvariantHandlerFailure.t.sol
* interlude: forgot to use a new file
* migrate InvariantInnerContract.t.sol
* migrate InvariantPreserveState.t.sol
* migrate InvariantReentrancy.t.sol
* migrate InvariantRollFork.t.sol
* migrate InvariantScrapeValues.t.sol
* migrate InvariantSequenceNoReverts.t.sol
* migrate InvariantShrinkBigSequence.t.sol
* migrate InvariantShrinkFailOnRevert.t.sol
* migrate InvariantShrinkWithAssert.t.sol
* migrate InvariantTest1.t.sol
* fix InvariantInnerContract.t.sol
* update new Rlp test
* com
* better com
* nuke tests/it
* test: fix testdata paths in script tester
* test: fix relative paths in test_cmd
* test: redact more in issue_2851
* fix: copy testdata correctly
* trace addrs
* manual retry logic with --retry
* fix nondeterministic output
* debug: fs lock error context
* test: fix project root for windows
* test: skip project root test if unset
* normalize both
* typo
* Revert "typo"
This reverts commit 402bea105c6f38b82664b50ca854f95e456df795.
* Revert "debug: fs lock error context"
This reverts commit e5caeddd1e4cb457d7b24d7d7fdfdb370e2feabf.
* fix
* fix: locked_write_line for windows
* chore: clippy
* fmt
* chore: speed up fuzzed_selected_targets
* other way
* fix nondeterministic output 2
* fix: disable persistence
* test: revert old via-ir
* ci: tweak cache key
* do not run trace test when isolate
---------
Co-authored-by: grandizzy <grandizzy.the.egg@gmail.com>
* fix(anvil): always disable nonce check (#12144)
* deps: bump deps (#12149)
* deps: bump deps
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* minimum Cargo.lock
---------
Co-authored-by: rplusq <rplusq@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com>
---------
Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com>
Co-authored-by: grandizzy <grandizzy.the.egg@gmail.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: Rafael Quintero <32346241+rplusq@users.noreply.github.com>
Co-authored-by: rplusq <rplusq@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
* Update test.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update test.yml (#167)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update test.yml (#168)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/ci.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update cargo.yml (#171)
CI/CD Configuration Update: The CircleCI configuration file, cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring the CI pipeline utilizes a more recent Rust toolchain.
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/ci_v1.yml (#173)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update cargo.yml (#174)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* chore(deps): bump taiki-e/install-action from 2.62.28 to 2.62.33 (#175)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.62.28 to 2.62.33.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/v2.62.28...e43a5023a747770bfcb71ae048541a681714b951)
---
updated-dependencies:
- dependency-name: taiki-e/install-action
dependency-version: 2.62.33
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Delete .circleci/cargo.yml (#179)
I Configuration Removal: The .circleci/cargo.yml file, which defined CircleCI jobs for building and testing Rust projects, has been completely removed from the repository.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/ci_v1.yml (#182)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update config.yml (#183)
Configuration File Cleanup: Removed an unnecessary blank line in the .circleci/config.yml file, improving its formatting and readability.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update config.yml (#187)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/config.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci directory
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update ci_v1.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update Rust Docker image version to 1.89.0
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 76: Artifact poisoning
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* chore(deps): bump alloy-dyn-abi in the cargo group across 1 directory
Bumps the cargo group with 1 update in the / directory: [alloy-dyn-abi](https://github.com/alloy-rs/core).
Updates `alloy-dyn-abi` from 0.8.25 to 0.8.26
- [Release notes](https://github.com/alloy-rs/core/releases)
- [Changelog](https://github.com/alloy-rs/core/blob/v0.8.26/CHANGELOG.md)
- [Commits](https://github.com/alloy-rs/core/compare/v0.8.25...v0.8.26)
---
updated-dependencies:
- dependency-name: alloy-dyn-abi
dependency-version: 0.8.26
dependency-type: direct:production
dependency-group: cargo
...
Signed-off-by: dependabot[bot] <support@github.com>
* Create ci-web3-gamefi.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 74: Artifact poisoning
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 83: Uncontrolled data used in path expression
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 93: Uncontrolled data used in path expression
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 76: Artifact poisoning
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 94: Uncontrolled data used in path expression
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 80: Server-side request forgery
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 80: Server-side request forgery
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Create codeql.yml (#208)
* Update ci.yml (#209)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
---------
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the Rust version in the CI from 1.88.0 to 1.89.0. While this is a good maintenance step, I've identified a potential improvement for your CI configuration. The project's Cargo.toml specifies a Minimum Supported Rust Version (MSRV) of 1.86, but the CI doesn't test against it. I've added a comment suggesting the addition of an MSRV check to prevent compatibility issues.
* Update cargo.yml (#210)
https://github.com/apps/gemini-code-assist
-------------------
Code Review
This pull request downgrades the Rust version in the CI pipeline from 1.88.0 to 1.87.0. This is inconsistent with the project's declared Minimum Supported Rust Version (MSRV) of 1.89 in Cargo.toml. My review highlights this discrepancy and suggests aligning the CI's Rust version with the MSRV to ensure the project's compatibility guarantees are properly tested.
---------------
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Foundry rs maste 1f4b36a (#214)
* Create jekyll.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Create docker-image.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 58: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update .github/workflows/docker-image.yml
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update docker-image.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Revert "chore: fix isolate tests (#10344)"
This reverts commit 70ded2b35f95ee9b4ee94f5e44961914d30a87f7.
* Delete .github/workflows/jekyll.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 19: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
---------
Signed-off-by: AU_gdev_19 <64915515+Dargon789@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>
* Update and rename docker-image.yml to docker.yml (#218)
Streamline the Docker CI workflow by renaming the file and enhancing it with scheduled runs, Buildx multi-platform builds, metadata tagging, conditional pushes, and automated image signing with Cosign.
CI:
Rename and replace the legacy docker-image.yml workflow with docker.yml
Add scheduled cron runs and triggers on pushes to master, semver tags, and PRs
Configure Docker Buildx for multi-platform builds with cache
Extract Docker metadata and conditionally push images to GHCR on non-PR events
Install Cosign and sign published Docker images using ephemeral identity tokens
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update ci.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Create docker-image.yml (#224)
CI:
Introduce docker-image.yml GitHub Actions workflow to checkout code and build Docker image on ubuntu-latest
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update config.yml (#225)
CI:
Insert comment lines to delineate and structure sections in .circleci/config.yml for enhanced clarity
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update sequence.rs (#226)
Enhancements:
Add standalone # lines in sequence.rs to serve as hidden placeholders for rustdoc examples
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update dependencies.yml (#227)
* Update dependencies.yml
Refactor the weekly dependencies workflow to inline cargo update steps, auto-generate commit messages and PR bodies with update logs, and use the create-pull-request action to open update PRs on a dedicated branch.
Enhancements:
Define environment variables for GitHub token, branch name, PR title, and PR body including cargo update logs
Inline checkout, Rust toolchain setup, and cargo update command with log cleanup instead of relying on an external workflow
Craft commit messages and PR bodies dynamically by capturing and formatting cargo update output
Use peter-evans/create-pull-request to push Cargo.lock updates to a 'cargo-update' branch
CI:
Move permissions and GitHub token configuration into the job context
Explicitly set the runner to ubuntu-latest and remove the top-level empty permissions block
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update .github/workflows/dependencies.yml
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[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: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
* Update npm.yml (#228)
CI:
Add comment to the Publish Binary step indicating it runs automatically after a successful release workflow or can be triggered manually with a run_id
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update snyk-container.yml (#229)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update nextest.yml (#230)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update const.ts (#231)
Code Formatting: Removed an extraneous blank line in npm/src/const.ts to improve code cleanliness and consistency.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Revert "Create web3_defi_gamefi.yml (#61)" (#233)
This reverts commit 8575916b7675f246b54daf70cfddccb3f5b97fb0.
* Create deploy.yml (#240)
* Create deploy.yml
CI:
Add GitHub Actions workflow to build the Rust project, run tests, and build a Docker image on pushes to main/master
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 106: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
---------
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
* Update dependencies.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update dependencies.yml (#247)
Improve readability of the GitHub Actions dependencies workflow by adjusting whitespace and adding blank lines
CI:
Add blank line before the workflow name declaration
Insert blank line after the scheduled cron job entry
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update dependencies.yml (#248)
CI:
Remove extraneous blank line in .github/workflows/dependencies.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update test.yml (#249)
CI:
Remove dev branch from test workflow triggers
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update Cargo.lock (#253)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update Cargo.lock (#254)
Chores:
Regenerate Cargo.lock to update dependencies
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Create config.yml (#255)
* Create config.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update .circleci/config.yml
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[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: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
* Update config.yml (#256)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* fix: upgrade tsdown from 0.15.12 to 0.16.1
Snyk has created this PR to upgrade tsdown from 0.15.12 to 0.16.1.
See this package in npm:
tsdown
See this project in Snyk:
https://app.snyk.io/org/dargon789/project/8da85645-409e-46fa-bd46-9b58e7905fb8?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr
* Create google.yml (#266)
CI:
Introduce a Google Cloud deployment workflow that builds a Docker image, pushes it to Artifact Registry, and deploys it to a GKE cluster on pushes to the main branches.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update flake.lock (#269)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update flake.nix (#270)
Adjust Nix flake development shell configuration for better cross-platform support and simplify dependencies.
Enhancements:
Remove the dprint dependency from the Nix development shell.
Add conditional AppKit framework linkage on Darwin systems in the Nix shell configuration.
Drop custom hardeningDisable settings from the Nix development shell definition.
https://github.com/apps/gemini-code-assist
Code Review
This pull request updates the Nix flake configuration to improve cross-platform support and simplify dependencies. The changes include removing dprint and hardeningDisable settings, and conditionally adding the AppKit framework for Darwin systems. While most changes are beneficial, removing dprint from the development shell dependencies while its configuration file remains could cause issues for contributors. I've added a comment regarding this potential inconsistency.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update Cargo.toml (#271)
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update nextest.toml (#272)
Adjust test runner configuration for nextest to better handle long-running and specific tests.
Enhancements:
Introduce a dedicated test group that limits chisel-serial tests to a single thread.
Increase the default slow-test timeout period to reduce premature terminations for longer-running tests.
Expand the slow-timeout override filter to include both ext_integration and can_test_forge_std tests.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update dprint.json (#273)
(https://github.com/apps/gemini-code-assist)
Code Review
This pull request updates the dprint.json configuration file. The changes correctly enable formatting for dprint.json itself by modifying the excludes list, update the JSON and Markdown dprint plugins to their latest versions, and add a final newline to the file for POSIX compliance. These are all good maintenance improvements. The changes have been reviewed and appear to be correct and beneficial. No issues were found.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update .github/workflows/apisec-scan.yml
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update counter/README.md
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update .github/ISSUE_TEMPLATE/bug_report.md
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Dependabot/cargo/cargo 38744a1864 (#282)
* chore(deps): bump alloy-dyn-abi in the cargo group across 1 directory
Bumps the cargo group with 1 update in the / directory: [alloy-dyn-abi](https://github.com/alloy-rs/core).
Updates `alloy-dyn-abi` from 0.8.25 to 0.8.26
- [Release notes](https://github.com/alloy-rs/core/releases)
- [Changelog](https://github.com/alloy-rs/core/blob/v0.8.26/CHANGELOG.md)
- [Commits](https://github.com/alloy-rs/core/compare/v0.8.25...v0.8.26)
---
updated-dependencies:
- dependency-name: alloy-dyn-abi
dependency-version: 0.8.26
dependency-type: direct:production
dependency-group: cargo
...
Signed-off-by: dependabot[bot] <support@github.com>
* Update and rename ci.yml to cargo.yml (#268)
Update CircleCI configuration to use a different Rust toolchain image and rename the workflow file.
Build:
Rename the CircleCI configuration file from ci.yml to cargo.yml.
Change the CircleCI Docker image to use Rust 1.78.0 instead of 1.88.0.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
---------
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Fix cloning of compiler settings for Vyper input
Replace context.clone().compiler_settings.vyper with
context.compiler_settings.vyper.clone() to avoid unnecessary
cloning of the entire VerificationContext. This reduces memory
allocations when creating VyperInput instances.
Applied to both etherscan and sourcify verification providers.
* Update config.yml (#283)
Summary by Sourcery
Update CircleCI pipeline to use a custom Docker executor and job tailored to the project instead of the example hello-world workflow.
Enhancements:
Introduce a reusable custom executor that pulls from the stable cimg/base Docker image with Docker Hub authentication.
CI:
Replace the sample say-hello job and workflow with a project-specific job and workflow wired to the new custom executor in .circleci/config.yml.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* fix: use network-specific BaseFeeParams for Optimism in Anvil
* Dargon789 patch 1 (#285)
* Update test.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update test.yml (#167)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/ci_v1.yml (#173)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update cargo.yml (#174)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .circleci/config.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 74: Artifact poisoning
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 83: Uncontrolled data used in path expression
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 93: Uncontrolled data used in path expression
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 76: Artifact poisoning
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 94: Uncontrolled data used in path expression
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 80: Server-side request forgery
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update cargo.yml (#210)
https://github.com/apps/gemini-code-assist
-------------------
Code Review
This pull request downgrades the Rust version in the CI pipeline from 1.88.0 to 1.87.0. This is inconsistent with the project's declared Minimum Supported Rust Version (MSRV) of 1.89 in Cargo.toml. My review highlights this discrepancy and suggests aligning the CI's Rust version with the MSRV to ensure the project's compatibility guarantees are properly tested.
---------------
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Fix cloning of compiler settings for Vyper input
Replace context.clone().compiler_settings.vyper with
context.compiler_settings.vyper.clone() to avoid unnecessary
cloning of the entire VerificationContext. This reduces memory
allocations when creating VyperInput instances.
Applied to both etherscan and sourcify verification providers.
---------
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: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: Gengar <creeptogengar@gmail.com>
* merge gh-master (#287)
* Create config.yml (#236)
Create .circleci/config.yml defining a version 2.1 pipeline with a docker-based "say-hello" job, checkout and echo steps, and a workflow to orchestrate it
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* fix(evm): use timestamp-based blob base fee calculation (#12959)
* fix(evm): use timestamp-based blob base fee calculation
* chore: use patch
* Now BPO1 is default
* bump to hardforks to 0.4.7
---------
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
* fix(config): reject bare versions in compilation restrictions (#12955)
fmt
Co-authored-by: tefyosL-sol <gasgoblinn@gmail.com>
* Revert "fix(config): err on unknown profile (#12946)" (#12964)
This reverts commit 6ff4b52e2e572e93d0cd81591b1bd0e6ad9ed507.
* Update crates/config/src/compilation.rs
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: cakevm <cakevm@proton.me>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: Theodore Solis <gasgobling@gmail.com>
Co-authored-by: tefyosL-sol <gasgoblinn@gmail.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* Foundry/ethereum ux (#284)
* Potential fix for code scanning alert no. 19: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 61: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 74: Artifact poisoning
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Create config.yml (#105)
* Create cargo.yml (#106)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .github/workflows/docker-image.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Revert "Create cargo.yml (#106)"
This reverts commit 251a2b4fce0c50e3426ffb2022d9abef5b948fa9.
* Create cargo.yml (#213)
https://github.com/apps/gemini-code-assist
Code Review
This pull request introduces a CircleCI workflow to automate formatting checks and tests. My review has identified two main issues in the configuration: redundant steps that would unnecessarily increase job execution time, and a mismatch between the Rust version in the CI environment and the one specified in the project's Cargo.toml. I've provided suggestions to fix these issues for a more efficient and consistent CI process.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.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: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
* Gamefi defi (#288)
* chore: ignore RUSTSEC-2025-0137 (#12941)
Co-authored-by: Claude <noreply@anthropic.com>
* chore(deps): weekly `cargo update` (#12940)
* chore(deps): weekly `cargo update`
Updating git repository `https://github.com/rust-cli/rexpect`
Updating git repository `https://github.com/paradigmxyz/solar.git`
Skipping git submodule `https://github.com/argotorg/solidity.git` due to update strategy in .gitmodules
Updating git repository `https://github.com/tempoxyz/tempo`
Updating git repository `https://github.com/paradigmxyz/reth`
Locking 71 packages to latest compatible versions
Updating alloy-chains v0.2.23 -> v0.2.24
Updating alloy-consensus v1.1.3 -> v1.2.1
Updating alloy-consensus-any v1.1.3 -> v1.2.1
Updating alloy-contract v1.1.3 -> v1.2.1
Updating alloy-dyn-abi v1.5.1 -> v1.5.2
Updating alloy-eip5792 v1.1.3 -> v1.2.1
Updating alloy-eips v1.1.3 -> v1.2.1
Updating alloy-ens v1.1.3 -> v1.2.1
Updating alloy-genesis v1.1.3 -> v1.2.1
Updating alloy-json-abi v1.5.1 -> v1.5.2
Updating alloy-json-rpc v1.1.3 -> v1.2.1
Updating alloy-network v1.1.3 -> v1.2.1
Updating alloy-network-primitives v1.1.3 -> v1.2.1
Updating alloy-primitives v1.5.1 -> v1.5.2
Updating alloy-provider v1.1.3 -> v1.2.1
Updating alloy-pubsub v1.1.3 -> v1.2.1
Updating alloy-rpc-client v1.1.3 -> v1.2.1
Updating alloy-rpc-types v1.1.3 -> v1.2.1
Updating alloy-rpc-types-anvil v1.1.3 -> v1.2.1
Updating alloy-rpc-types-any v1.1.3 -> v1.2.1
Updating alloy-rpc-types-beacon v1.1.3 -> v1.2.1
Updating alloy-rpc-types-debug v1.1.3 -> v1.2.1
Updating alloy-rpc-types-engine v1.1.3 -> v1.2.1
Updating alloy-rpc-types-eth v1.1.3 -> v1.2.1
Updating alloy-rpc-types-trace v1.1.3 -> v1.2.1
Updating alloy-rpc-types-txpool v1.1.3 -> v1.2.1
Updating alloy-serde v1.1.3 -> v1.2.1
Updating alloy-signer v1.1.3 -> v1.2.1
Updating alloy-signer-aws v1.1.3 -> v1.2.1
Updating alloy-signer-gcp v1.1.3 -> v1.2.1
Updating alloy-signer-ledger v1.1.3 -> v1.2.1
Updating alloy-signer-local v1.1.3 -> v1.2.1
Updating alloy-signer-trezor v1.1.3 -> v1.2.1
Updating alloy-signer-turnkey v1.1.3 -> v1.2.1
Updating alloy-sol-macro v1.5.1 -> v1.5.2
Updating alloy-sol-macro-expander v1.5.1 -> v1.5.2
Updating alloy-sol-macro-input v1.5.1 -> v1.5.2
Updating alloy-sol-type-parser v1.5.1 -> v1.5.2
Updating alloy-sol-types v1.5.1 -> v1.5.2
Updating alloy-transport v1.1.3 -> v1.2.1
Updating alloy-transport-http v1.1.3 -> v1.2.1
Updating alloy-transport-ipc v1.1.3 -> v1.2.1
Updating alloy-transport-ws v1.1.3 -> v1.2.1
Updating alloy-trie v0.9.1 -> v0.9.2
Updating alloy-tx-macros v1.1.3 -> v1.2.1
Unchanged annotate-snippets v0.12.5 (available: v0.12.10)
Unchanged anstyle-svg v0.1.11 (available: v0.1.12)
Downgrading aws-smithy-runtime v1.9.6 -> v1.9.5
Updating axum-core v0.5.5 -> v0.5.6
Updating cc v1.2.50 -> v1.2.51
Updating derive_more v2.1.0 -> v2.1.1
Updating derive_more-impl v2.1.0 -> v2.1.1
Updating dtoa v1.0.10 -> v1.0.11
Updating find-msvc-tools v0.1.5 -> v0.1.6
Unchanged generic-array v0.14.7 (available: v0.14.9)
Unchanged icu_collections v2.0.0 (available: v2.1.1)
Unchanged icu_normalizer v2.0.1 (available: v2.1.1)
Unchanged icu_normalizer_data v2.0.0 (available: v2.1.1)
Unchanged icu_properties v2.0.2 (available: v2.1.2)
Unchanged icu_properties_data v2.0.1 (available: v2.1.2)
Unchanged idna_adapter v1.1.0 (available: v1.2.1)
Updating itoa v1.0.15 -> v1.0.17
Updating jiff v0.2.16 -> v0.2.17
Updating jiff-static v0.2.16 -> v0.2.17
Updating libredox v0.1.11 -> v0.1.12
Updating libz-rs-sys v0.5.4 -> v0.5.5
Unchanged matchit v0.8.4 (available: v0.8.6)
Unchanged mdbook v0.4.52 (available: v0.5.2)
Updating portable-atomic v1.12.0 -> v1.13.0
Updating proc-macro2 v1.0.103 -> v1.0.104
Unchanged protobuf v3.3.0 (available: v3.7.2)
Unchanged protobuf-support v3.3.0 (available: v3.7.2)
Unchanged rand v0.8.5 (available: v0.9.2)
Unchanged ratatui v0.29.0 (available: v0.30.0)
Updating reqwest v0.12.26 -> v0.12.28
Updating ruint v1.17.0 -> v1.17.1
Updating rustix v1.1.2 -> v1.1.3
Updating ryu v1.0.21 -> v1.0.22
Updating schemars v1.1.0 -> v1.2.0
Updating schemars_derive v1.1.0 -> v1.2.0
Updating serde_json v1.0.145 -> v1.0.148
Updating signal-hook-registry v1.4.7 -> v1.4.8
Updating syn-solidity v1.5.1 -> v1.5.2
Updating tempfile v3.23.0 -> v3.24.0
Unchanged trezor-client v0.1.4 (available: v0.1.5)
Unchanged unicode-width v0.2.0 (available: v0.2.2)
Unchanged vergen v8.3.2 (available: v9.0.6)
Updating zlib-rs v0.5.4 -> v0.5.5
Adding zmij v1.0.0
note: to see how you depend on a package, run `cargo tree --invert <dep>@<ver>`
* touchups
* touchups
---------
Co-authored-by: mattsse <19890894+mattsse@users.noreply.github.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
* Update flake.lock (#12939)
flake.lock: Update
Flake lock file updates:
• Updated input 'fenix':
'github:nix-community/fenix/16642c5' (2025-12-20)
→ 'github:nix-community/fenix/3479aaf' (2025-12-27)
• Updated input 'fenix/rust-analyzer-src':
'github:rust-lang/rust-analyzer/ea1d299' (2025-12-18)
→ 'github:rust-lang/rust-analyzer/8c5a68e' (2025-12-26)
• Updated input 'nixpkgs':
'github:NixOS/nixpkgs/7d853e5' (2025-12-19)
→ 'github:NixOS/nixpkgs/3edc4a3' (2025-12-27)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com>
* fix(chisel): uninitalized variables (#12937)
* chore(deps): bump Swatinem/rust-cache from 2.8.1 to 2.8.2 (#12919)
Bumps [Swatinem/rust-cache](https://github.com/swatinem/rust-cache) from 2.8.1 to 2.8.2.
- [Release notes](https://github.com/swatinem/rust-cache/releases)
- [Changelog](https://github.com/Swatinem/rust-cache/blob/master/CHANGELOG.md)
- [Commits](https://github.com/swatinem/rust-cache/compare/f13886b937689c021905a6b90929199931d60db1...779680da715d629ac1d338a641029a2f4372abb5)
---
updated-dependencies:
- dependency-name: Swatinem/rust-cache
dependency-version: 2.8.2
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
* chore(deps): bump peter-evans/create-pull-request from 7.0.11 to 8.0.0 (#12918)
Bumps [peter-evans/create-pull-request](https://github.com/peter-evans/create-pull-request) from 7.0.11 to 8.0.0.
- [Release notes](https://github.com/peter-evans/create-pull-request/releases)
- [Commits](https://github.com/peter-evans/create-pull-request/compare/22a9089034f40e5a961c8808d113e2c98fb63676...98357b18bf14b5342f975ff684046ec3b2a07725)
---
updated-dependencies:
- dependency-name: peter-evans/create-pull-request
dependency-version: 8.0.0
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
* chore: sepolia rpc url (#12945)
chore: sepolia rpc url private
* chore(deps): bump crate-ci/typos from 1.40.0 to 1.40.1 (#12949)
Bumps [crate-ci/typos](https://github.com/crate-ci/typos) from 1.40.0 to 1.40.1.
- [Release notes](https://github.com/crate-ci/typos/releases)
- [Changelog](https://github.com/crate-ci/typos/blob/master/CHANGELOG.md)
- [Commits](https://github.com/crate-ci/typos/compare/2d0ce569feab1f8752f1dde43cc2f2aa53236e06...1a319b54cc9e3b333fed6a5c88ba1a90324da514)
---
updated-dependencies:
- dependency-name: crate-ci/typos
dependency-version: 1.40.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* chore(deps): bump DeterminateSystems/determinate-nix-action from 3.15.0 to 3.15.1 (#12950)
chore(deps): bump DeterminateSystems/determinate-nix-action
Bumps [DeterminateSystems/determinate-nix-action](https://github.com/determinatesystems/determinate-nix-action) from 3.15.0 to 3.15.1.
- [Release notes](https://github.com/determinatesystems/determinate-nix-action/releases)
- [Commits](https://github.com/determinatesystems/determinate-nix-action/compare/95732e95d70db3ba1e0adc26a63c5e0375aba78c...1d699fc25db3f9e079cd2f168ca007a4183389be)
---
updated-dependencies:
- dependency-name: DeterminateSystems/determinate-nix-action
dependency-version: 3.15.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* chore(deps): bump taiki-e/install-action from 2.65.1 to 2.65.7 (#12951)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.65.1 to 2.65.7.
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/taiki-e/install-action/compare/b9c5db3aef04caffaf95a1d03931de10fb2a140f...4c6723ec9c638cccae824b8957c5085b695c8085)
---
updated-dependencies:
- dependency-name: taiki-e/install-action
dependency-version: 2.65.7
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix(config): err on unknown profile (#12946)
* test: remove duplicate Issue2851 test (#12953)
* chore(cheats): make sign(Wallet) pure (#12912)
* chore(cheats): make sign(Wallet) pure
* ignore
---------
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
* fix(evm): use timestamp-based blob base fee calculation (#12959)
* fix(evm): use timestamp-based blob base fee calculation
* chore: use patch
* Now BPO1 is default
* bump to hardforks to 0.4.7
---------
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
* fix(config): reject bare versions in compilation restrictions (#12955)
fmt
Co-authored-by: tefyosL-sol <gasgoblinn@gmail.com>
* Revert "fix(config): err on unknown profile (#12946)" (#12964)
This reverts commit 6ff4b52e2e572e93d0cd81591b1bd0e6ad9ed507.
* fix(anvil): use B256 instead of TxHash for block hash parameters (#12961)
Update mod.rs
* Update crates/config/src/compilation.rs
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
---------
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: mattsse <19890894+mattsse@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: DaniPopes <57450786+DaniPopes@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com>
Co-authored-by: cakevm <cakevm@proton.me>
Co-authored-by: Theodore Solis <gasgobling@gmail.com>
Co-authored-by: tefyosL-sol <gasgoblinn@gmail.com>
Co-authored-by: Desant pivo <pivasdesant@gmail.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
* Create ci-web3-gamefi.yml (#217) (#289)
Introduce a basic CircleCI pipeline for the web3 GameFi project, providing a custom Docker executor and a stub job within a workflow.
CI:
Add CircleCI config file ci-web3-gamefi.yml with version 2.1 pipeline
Define a custom executor using the cimg/base:stable Docker image with Docker Hub credentials
Create a web3-defi-game-project- job and integrate it into a my-custom-workflow
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Merge pull request #47 (#290)
* Add .circleci/config.yml
* Updated config.yml
* Updated config.yml
* Updated config.yml
* Update test.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 19: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update test.yml (#46)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* chore(deps): bump revm to 24.0.0 (#10601)
* feat: implement add_balance endpoint (#10636)
* fix(bindings): ensure forge bind generates snake_case file names (#10622)
* fix(bindings): ensure forge bind generates snake_case file names
* refactor: use heck crate for snake_case conversion
---------
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
* chore: standardize lint help + validate docs existance (#10639)
* feat(cast mktx): add support for "--ethsign" option (#10641)
- Sign transactions using "eth_signTransaction" on local node with unlocked accounts.
- Same TX building logic as in "cast send --unlocked".
- Added a test case to validate the new functionality.
* chore(wallets): improve error message for signer instantiation failure (#10646)
chore(wallets): improve error message on signer instantiation failure
* chore: replaced anvil hardforks with alloy hardforks (#10612)
* chore: replaced anvil hardforks with alloy hardforks
* fixes
* fixes
* fixes
* removed redundant op and alloy hardforks enum
* fixes
* fixes
* bumped alloy hardforks and kept default to prague and isthmus
* bumped alloy-hardforks and fixes
---------
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
* fix(`anvil`): latest evm version should be prague (#10653)
* fix(`anvil`): latest evm version should be prague
* fix test
* nit
* chore(deps): bump tracing-subscriber (#51)
Bumps the cargo group with 1 update in the / directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).
Updates `tracing-subscriber` from 0.3.19 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.19...tracing-subscriber-0.3.20)
---
updated-dependencies:
- dependency-name: tracing-subscriber
dependency-version: 0.3.20
dependency-type: direct:production
dependency-group: cargo
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Update test.yml (#52)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update docker-image.yml (#53)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Create ci_cargo.yml (#59)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Create web3_defi_gamefi.yml (#61)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update dependencies.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 21: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Update dependencies.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update dependencies.yml (#247)
Improve readability of the GitHub Actions dependencies workflow by adjusting whitespace and adding blank lines
CI:
Add blank line before the workflow name declaration
Insert blank line after the scheduled cron job entry
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update dependencies.yml (#248)
CI:
Remove extraneous blank line in .github/workflows/dependencies.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update test.yml (#249)
CI:
Remove dev branch from test workflow triggers
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
---------
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
Co-authored-by: pistomat <pistomat@users.noreply.github.com>
Co-authored-by: zark <77061323+zarkk01@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com>
Co-authored-by: Ishika Choudhury <117741714+Rimeeeeee@users.noreply.github.com>
Co-authored-by: Yash Atreya <44857776+yash-atreya@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Update crates/evm/evm/src/executors/corpus.rs
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>
* Foundry/master test ux (#295)
* Update ci.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update ci.yml (#211)
This pull request updates the Rust version in the CircleCI workflow to 1.89.0. This is a good maintenance task to keep the CI environment up-to-date. I have one suggestion regarding the Docker image tag to potentially simplify future maintenance by automatically adopting patch releases. Overall, the change is correct and beneficial.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Update test.yml (#250)
CI:
Include the 'main' branch in the push event triggers for the test workflow
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
---------
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* fix(fmt): handle trailing coments between base contracts (#296)
@0xrusowsky @Dargon789 fix(fmt): handle trailing coments between base contracts Revert 142 master (#296)
* Create ci_cargo.yml (#72)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Create config.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Rename ci_cargo.yml to cargo.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* fix(fmt): handle trailing coments between base contracts (#12127)
* fix(fmt): account for ternary operators when estimating size
* fix(fmt): handle comments between inherited base contracts
* test: layout + base inheritance
* Revert "fix(fmt): handle trailing coments between base contracts (#12127)"
This reverts commit b8b5fbb83fa2436063cebc34ddf900abc972b11d.
* Update cargo.yml (#172)
CI/CD Configuration Update: The CircleCI configuration file, .circleci/cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring builds and tests run with the latest stable Rust toolchain.
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Fix cloning of compiler settings for Vyper input
Replace context.clone().compiler_settings.vyper with
context.compiler_settings.vyper.clone() to avoid unnecessary
cloning of the entire VerificationContext. This reduces memory
allocations when creating VyperInput instances.
Applied to both etherscan and sourcify verification providers.
* Remove duplicate logic in TxSigner::address() implementations
---------
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Gengar <creeptogengar@gmail.com>
Co-authored-by: Aganis <aganisgash@gmail.com>
* fix(fmt): handle trailing coments between base contracts (#296) (#299)
@0xrusowsky @Dargon789 fix(fmt): handle trailing coments between base contracts Revert 142 master (#296)
* Create ci_cargo.yml (#72)
* Create config.yml
* Rename ci_cargo.yml to cargo.yml
* fix(fmt): handle trailing coments between base contracts (#12127)
* fix(fmt): account for ternary operators when estimating size
* fix(fmt): handle comments between inherited base contracts
* test: layout + base inheritance
* Revert "fix(fmt): handle trailing coments between base contracts (#12127)"
This reverts commit b8b5fbb83fa2436063cebc34ddf900abc972b11d.
* Update cargo.yml (#172)
CI/CD Configuration Update: The CircleCI configuration file, .circleci/cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring builds and tests run with the latest stable Rust toolchain.
* Fix cloning of compiler settings for Vyper input
Replace context.clone().compiler_settings.vyper with
context.compiler_settings.vyper.clone() to avoid unnecessary
cloning of the entire VerificationContext. This reduces memory
allocations when creating VyperInput instances.
Applied to both etherscan and sourcify verification providers.
* Remove duplicate logic in TxSigner::address() implementations
---------
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Gengar <creeptogengar@gmail.com>
Co-authored-by: Aganis <aganisgash@gmail.com>
* Update CircleCI configuration for dev stage (#300)
fix Automatic reruns provide a safety net for your CI/CD pipelines by automatically retrying failed steps and/or workflows. Automatic reruns help teams maintain productivity by reducing the need for manual intervention when steps and workflows fail due to temporary issues.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* EIP-4788 implementation
* formatting
* add beacon block root tests
* Update crates/evm/evm/src/executors/trace.rs
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>
* Update crates/cast/src/cmd/run.rs
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>
* feat: upgrade @types/node from 24.10.4 to 25.0.2
Snyk has created this PR to upgrade @types/node from 24.10.4 to 25.0.2.
See this package in npm:
@types/node
See this project in Snyk:
https://app.snyk.io/org/dargon789/project/8da85645-409e-46fa-bd46-9b58e7905fb8?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr
* fix: `svm fails to download solc 0.8.33 on linux/arm64`, bump `svm-rs` (#13007) (#309)
bump svm-rs
Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com>
* Ethereumjs/master (#310)
* Potential fix for code scanning alert no. 19: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 61: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Potential fix for code scanning alert no. 74: Artifact poisoning
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Create config.yml (#105)
* Create cargo.yml (#106)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Delete .github/workflows/docker-image.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Rename ci_cargo.yml to cargo.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* fix(fmt): handle trailing coments between base contracts (#12127)
* fix(fmt): account for ternary operators when estimating size
* fix(fmt): handle comments between inherited base contracts
* test: layout + base inheritance
* Revert "fix(fmt): handle trailing coments between base contracts (#12127)"
This reverts commit b8b5fbb83fa2436063cebc34ddf900abc972b11d.
* Update cargo.yml (#172)
CI/CD Configuration Update: The CircleCI configuration file, .circleci/cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring builds and tests run with the latest stable Rust toolchain.
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Revert "Create cargo.yml (#106)"
This reverts commit 251a2b4fce0c50e3426ffb2022d9abef5b948fa9.
* Create cargo.yml (#213)
https://github.com/apps/gemini-code-assist
Code Review
This pull request introduces a CircleCI workflow to automate formatting checks and tests. My review has identified two main issues in the configuration: redundant steps that would unnecessarily increase job execution time, and a mismatch between the Rust version in the CI environment and the one specified in the project's Cargo.toml. I've provided suggestions to fix these issues for a more efficient and consistent CI process.
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Create docker.yml
Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
* Remove duplicate logic in TxSigner::address() implementations
* fix(fmt): handle trailing coments between base contracts (#296)
@0xrusowsky @Dargon789 fix(fmt): handle trailing coments between base contracts Revert 142 master (#296)
* Create ci_cargo.yml (#72)
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Create config.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Rename ci_cargo.yml to cargo.yml
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* fix(fmt): handle trailing coments between base contracts (#12127)
* fix(fmt): account for ternary operators when estimating size
* fix(fmt): handle comments between inherited base contracts
* test: layout + base inheritance
* Revert "fix(fmt): handle trailing coments between base contracts (#12127)"
This reverts commit b8b5fbb83fa2436063cebc34ddf900abc972b11d.
* Update cargo.yml (#172)
CI/CD Configuration Update: The CircleCI configuration file, .circleci/cargo.yml, has been updated to use a newer version of the Rust Docker image.
Rust Toolchain Version Bump: The cimg/rust Docker image version has been incremented from 1.88.0 to 1.89.0, ensuring builds and tests run with the latest stable Rust toolchain.
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
* Fix cloning of compiler settings for Vyper input
Replace context.clone().compiler_settings.vyper with
context.compiler_settings.vyper.clone() to avoid unnecessary
cloning of the entire VerificationContext. This reduces memory
allocations when creating VyperInput instances.
Applied to both etherscan and sourcify verification providers.
* Remove duplicate logic in TxSigner::address() implementations
---------
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Gengar <creeptogengar@gmail.com>
Co-authored-by: Aganis <aganisgash@gmail.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: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
Co-authored-by: Aganis <aganisgash@gmail.com>
Co-authored-by: Gengar <creeptogengar@gmail.com>
* Forge/master (#311)
* Potential fix for code scanning alert no. 19: Workflow does not contain permissions
Co-authored-by: Copilot Autofix powered b…
…#14683) (#552) feat: add Amsterdam hardfork mapping to SpecId Add EthereumHardfork::Amsterdam => SpecId::AMSTERDAM mapping in spec_id_from_ethereum_hardfork. Without this, Amsterdam would hit the unreachable!() catch-all arm. The default evm_version is already set to Osaka. Amp-Thread-ID: https://ampcode.com/threads/T-019e113f-5bda-711b-8ec5-4841042ba62c Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com> Co-authored-by: Centaur AI <ai@centaur.local>
…553) * feat: add Amsterdam hardfork mapping and default to Osaka (foundry-rs#14683) feat: add Amsterdam hardfork mapping to SpecId Add EthereumHardfork::Amsterdam => SpecId::AMSTERDAM mapping in spec_id_from_ethereum_hardfork. Without this, Amsterdam would hit the unreachable!() catch-all arm. The default evm_version is already set to Osaka. Amp-Thread-ID: https://ampcode.com/threads/T-019e113f-5bda-711b-8ec5-4841042ba62c Co-authored-by: Centaur AI <ai@centaur.local> * test: mark Issue14212Test as flaky (Base RPC failures) (foundry-rs#14690) Issue14212Test (test_rollForkToTxOnBase, test_transactDepositTxOnBase) depends on Base RPCs to fetch tx 0xe2f4bff... which intermittently fails with 'could not get transaction'. This is the same class of flakiness as the existing Polygon RPC skip. Move the contract into FLAKY_TESTDATA_CONTRACTS so it runs in the nightly flaky profile instead of blocking every CI run. Amp-Thread-ID: https://ampcode.com/threads/T-019e15de-2292-74cf-a885-b65acaa41d3c Co-authored-by: Centaur AI <ai@centaur.local> * feat: improve forge build lint-failure UX (foundry-rs#14676) * feat: improve forge build lint-failure UX * dedup lint-failure bypass message and revert parse emitter to stderr * address review: lead with bug-report CTA, add failure-notice tests - Rewrite LINT_FAILURE_NOTICE to lead with the report-the-bug CTA (deep-linked to BUG-FORM.yml) and demote --no-lint to a per-run workaround, with a docs link for temporarily disabling lint-on-build. - Drop the RUST_BACKTRACE suggestion: the failure is an eyre error built at a single call site, so a backtrace adds no signal. - Add integration tests for the failure notice (positive + negative --no-lint case) using COUNTER_A + deny=Notes to deterministically trigger the lint Err path without breaking compilation. - Add unit tests for the new convert_solar_errors non-buffer branch covering singular/plural messaging and the no-error path. Amp-Thread-ID: https://ampcode.com/threads/T-019e15e7-6907-723c-bd10-ac64558ed4ce Co-authored-by: Amp <amp@ampcode.com> * fix: fmt * use snapshot assertions for failure-notice tests; trim doc comment - Replace the fan-out of assert!(stderr.contains(...)) checks with a single snapbox stderr_eq snapshot, so the full expected output (lint diagnostic + notice + eyre cause chain) lives in one place and is trivially refreshed via SNAPSHOTS=overwrite. - Snapshot the negative --no-lint case as empty stderr too. - Drop the verbose doc comment on LINT_FAILURE_NOTICE; the constant's contents already speak for themselves. - Trim 'attach the full `forge build` output' to the more general 'attach the full output above'. Amp-Thread-ID: https://ampcode.com/threads/T-019e15e7-6907-723c-bd10-ac64558ed4ce Co-authored-by: Amp <amp@ampcode.com> * trim verbose test comments Amp-Thread-ID: https://ampcode.com/threads/T-019e15e7-6907-723c-bd10-ac64558ed4ce Co-authored-by: Amp <amp@ampcode.com> --------- Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com> Co-authored-by: Amp <amp@ampcode.com> Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com> * feat(invariant): assert all invariants by default (`assert_all`) (foundry-rs#12587) * feat(invariant): assert all invariants * Tests and Nits Amp-Thread-ID: https://ampcode.com/threads/T-019dbf48-3fb0-7762-a01f-b5e966339e73 Co-authored-by: Amp <amp@ampcode.com> * fix: check all invariants in afterInvariant gate and preflight Amp-Thread-ID: https://ampcode.com/threads/T-019dbf48-3fb0-7762-a01f-b5e966339e73 Co-authored-by: Amp <amp@ampcode.com> * fix: use per-invariant fail_on_revert when recording handler revert failures Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dbf48-3fb0-7762-a01f-b5e966339e73 * fix: commit state between txs in generate_counterexample Amp-Thread-ID: https://ampcode.com/threads/T-019dbf48-3fb0-7762-a01f-b5e966339e73 Co-authored-by: Amp <amp@ampcode.com> * fix: preflight check all invariants, not just primary Amp-Thread-ID: https://ampcode.com/threads/T-019dbf48-3fb0-7762-a01f-b5e966339e73 Co-authored-by: Amp <amp@ampcode.com> * fix: exclude secondary invariants from optimization mode runs Amp-Thread-ID: https://ampcode.com/threads/T-019dbf48-3fb0-7762-a01f-b5e966339e73 Co-authored-by: Amp <amp@ampcode.com> * refactor: rename invariant_fn to primary_invariant_fn, deterministic preflight error, debug_assert on empty invariants Amp-Thread-ID: https://ampcode.com/threads/T-019dbf48-3fb0-7762-a01f-b5e966339e73 Co-authored-by: Amp <amp@ampcode.com> * feat: show broken invariant count in progress bar during continuous runs Amp-Thread-ID: https://ampcode.com/threads/T-019dbf48-3fb0-7762-a01f-b5e966339e73 Co-authored-by: Amp <amp@ampcode.com> * feat(invariant): rename continuous_run to assert_all and default to true Renames the InvariantConfig field to better describe its semantics ("assert every invariant in the suite, don't stop on first failure") and flips the default to true so multi-invariant suites report all broken invariants by default, matching Echidna/Medusa behavior. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dcd68-66ac-76ed-ac5c-7ea722a9c9ae * feat(invariant): parameterize shrinker by target invariant + persisted failures footer - Generalize shrink_sequence, shrink_sequence_value, replay_run, replay_error to accept target_invariant: &Function (currently always primary; unblocks per-secondary shrinking). - Move reset_shrink_progress out of shrink fns; called once per invariant from replay_error. Progress label now 'Shrink: <invariant_name>'. - Add TestResult.invariant_failure_dir; Display appends 'N invariant failures persisted to <dir> — rerun to shrink' when secondary failures were written. Amp-Thread-ID: https://ampcode.com/threads/T-019dcd68-66ac-76ed-ac5c-7ea722a9c9ae Co-authored-by: Amp <amp@ampcode.com> * feat(invariant): structured InvariantOtherFailure for assert_all secondaries Promotes TestResult.other_failures from Vec<String> to Vec<InvariantOtherFailure> carrying name, reason, optional counterexample, and persisted path. Display renders each secondary symmetrically with [FAIL: reason] + [Sequence] block when a counterexample is available, falling back to the terse 'name: reason' one-liner otherwise. Amp-Thread-ID: https://ampcode.com/threads/T-019dcd68-66ac-76ed-ac5c-7ea722a9c9ae Co-authored-by: Amp <amp@ampcode.com> * feat(invariant): serial secondary shrinking + Ctrl-C persists un-shrunk secondaries PR-3 of the assert_all rollout. After the campaign finishes, every broken secondary invariant is shrunk in turn via replay_error so users get a ready-to-debug counterexample for each failure in a single run (matching how the primary is rendered: [FAIL: reason] <name> + [Sequence] block). On Ctrl-C, instead of dropping known secondaries (previous behavior was a 'break' before pushing them), the loop keeps recording every failure the campaign discovered. The shrink + replay step is skipped to honor the interrupt, but the un-shrunk sequence is persisted via BaseCounterExample::from_invariant_call (no execution required), so a re-run targeting that secondary picks up the saved counterexample and shrinks from there — same UX as re-running an interrupted primary. Output of an interrupted run now includes a terse '<invariant>: <reason>' line for each secondary the campaign saw, preserving visibility of all broken invariants while keeping the interrupt fast. Adds e2e coverage: - assert_all: extended to verify secondary failures render symmetrically with shrunk sequences and that re-running skips persisted secondaries. - assert_all_only_primary: new test confirming no secondary [FAIL] blocks or persisted-failures footer appear when only the primary breaks. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dcdd3-53f5-76b6-ac36-d59f06b58280 * feat(invariant): assert_all polish — [i/N] shrink counter, suite roll-up, opt-mode warning Three small UX wins for assert_all campaigns. No behavior change, no new dependencies. 1. Shrink progress bar gets an [i/N] queue counter when more than one invariant needs shrinking, so users see how many shrinkers are queued behind the current one (e.g. '[2/3] Shrink: invariant_X'). reset_shrink_progress and replay_error gain a position parameter; single-invariant call sites pass None. 2. Suite-level roll-up footer: when assert_all exercised >1 invariant and the test failed, render 'Suite assert_all: <broken>/<total> invariants broken' above the per-invariant blocks. Gives CI logs and Slack pastes a glanceable health line. New Option<usize> field on TestResult, populated only when meaningful. 3. Startup warning when assert_all + optimization-mode are combined. Optimization mode tracks one int256 return value, so any boolean secondary invariants in the same contract are filtered out before the campaign — previously silent. Now emits a once-per-suite warning naming the optimization invariant and every dropped boolean so users can move them to a separate contract. E2E tests: extend assert_all to assert the new 4/5 roll-up; assert_all_only_primary covers the 1/2 case; new assert_all_optimization_mode_warning verifies the warning fires with the dropped invariant names. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dcdd3-53f5-76b6-ac36-d59f06b58280 * feat(invariant): warn when assert_all skips invariants with persisted failures Symmetric with the primary's existing persisted-replay warning. Echidna and Medusa never silently drop properties between runs — properties are re-evaluated every campaign and a previous failure doesn't suppress them. Foundry's per-property failure file model meant secondaries with a stale persisted counterexample were filtered out of the campaign with no acknowledgment, so users coming from Echidna/Medusa would see fewer invariants in the report than their contract defines. Now emits one stderr line listing every skipped name and the cache dir to clean, e.g.: Warning: test/X.t.sol:Suite: 3 invariant(s) skipped due to persisted failures: invariant_a, invariant_b, invariant_c. Run `forge clean` or delete files in cache/invariant/failures/Suite to re-include. E2E: extends assert_all re-run case with stderr_eq snapshot asserting the warning fires with all 3 skipped names. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dcdd3-53f5-76b6-ac36-d59f06b58280 * fix(invariant): gate afterInvariant per-run under assert_all Previously afterInvariant was gated on failures.errors.is_empty() campaign-wide. Under assert_all that gate stayed closed for the rest of the campaign once any invariant broke, silently skipping the afterInvariant hook on every subsequent run. Any assertions or cleanup logic in afterInvariant therefore stopped running after the first unrelated invariant failure. Now snapshot failures.errors.len() at the start of each run and only skip afterInvariant when the current run produced a new failure. Preserves the legacy 'don't run afterInvariant on a run that already failed' semantics while letting it run on subsequent runs once an earlier invariant has broken. E2E: new assert_all_after_invariant_runs_after_earlier_failure case breaks invariant_first in run 1, keeps the campaign alive with a second never-breaking invariant, and asserts an always-reverting afterInvariant surfaces its marker in failure output. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dce2d-57c7-734a-bbc6-6fa5e34b25de * fix(invariant): re-evaluate secondary persisted failures on settings change The secondary persisted-failure skip used a bare `.exists()` check at two sites in runner.rs (the warning + InvariantContract::new filter, and the post-campaign shrink loop). Under the new `assert_all = true` default this meant any leftover failure file from a previous run was treated as still valid even after the user changed a tracked setting (target contracts/selectors, target/excluded senders, fail_on_revert), silently dropping the secondary from the campaign with a misleading 'skipped due to persisted failures' warning. Now both sites use the same settings-aware compatibility check the primary's replay path uses (persisted_call_sequence settings.diff). Stale caches fall back to a fresh evaluation; only secondaries whose persisted settings still match the current run are honored. Also hoists current_settings up so the new secondary_has_compatible_persisted closure can reuse it across all three call sites (warning, filter, shrink-loop skip). E2E: new assert_all_secondary_persisted_revalidates_on_settings_change runs once with fail_on_revert=false, flips it to true, re-runs and asserts the suite roll-up shows 2/2 invariants broken — proving the secondary was re-evaluated rather than silently filtered out. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dce2d-57c7-734a-bbc6-6fa5e34b25de * fix(invariant): drop hollow [FAIL] when only secondaries break under assert_all When the selected invariant test passes but a secondary breaks under assert_all, the report previously rendered a hollow '[FAIL]' header (no reason, no counterexample) for the primary and the suite roll-up overcounted broken invariants as '1 + other_failures.len()', attributing a non-existent primary failure. Now key the primary header on whether the primary actually broke (`reason.is_some() || counterexample.is_some()`) and skip the header when it didn't. Roll-up uses the same flag so the count reflects only invariants that actually broke (e.g., 1/2 instead of 2/2). JSON shape is unchanged: top-level reason/counterexample stay null when the selected primary didn't break, with full secondary detail in other_failures. E2E: new assert_all_secondary_only_failure_no_hollow_fail asserts a secondary-only break renders 'Suite assert_all: 1/2 invariants broken' followed by the secondary's '[FAIL: ...] <name>' block, with no hollow primary header. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dce2d-57c7-734a-bbc6-6fa5e34b25de * fix(invariant): scope assert_all hollow [FAIL] suppression to secondary-only case Previous commit suppressed the '[FAIL]' header whenever the primary had no top-level reason or counterexample, which also matches DS-style failures (they signal via the 'failed' flag and log events rather than through TestResult.reason). That regressed failure_assertions::ds_style_test_failing and test_cmd::core::legacy_assertions in CI. Now the suppression is scoped strictly to the assert_all secondary-only case: skip the primary header only when no primary failure AND assert_all is in play AND there is at least one secondary to render. DS-style, plain unit and single-invariant failures keep the original '[FAIL]'/'[FAIL: ...]' rendering. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dce2d-57c7-734a-bbc6-6fa5e34b25de * fix(invariant): attribute failure event to first broken invariant in declaration order The structured JSON 'failure' event emitted to stderr at campaign end (consumed by benchmark and CI tooling) used 'errors.values().next()' on a HashMap to pick its 'reason' field, while hardcoding the 'invariant' field to the primary's name. With HashMap RandomState, the same broken set of invariants produced a different reason string across runs, and the event was self-inconsistent (e.g., 'invariant: invariant_balance, reason: fee miscalculation'). Three sites used this pattern: in-run break path, afterInvariant break path, and the preflight check fallback. Now they walk 'invariant_contract.invariant_fns' in declaration order (a Vec, deterministic) and pick the first one with a recorded failure. Both 'invariant' and 'reason' fields refer to the same function, and the event is stable across runs. A new 'first_broken_event' helper centralizes the lookup. E2E: assert_all_failure_event_uses_declaration_order declares three invariants (a, b, c) that all break on the same call, runs with '--mt invariant_c' (primary is the last declared) and asserts the emitted event names invariant_a with reason 'a broken'. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dce2d-57c7-734a-bbc6-6fa5e34b25de * refactor(invariant): rename to InvariantSecondaryFailure / invariant_secondary_failures and serialize sparsely Renames TestResult.other_failures -> invariant_secondary_failures and the underlying InvariantOtherFailure struct -> InvariantSecondaryFailure. The previous names were generic ('other relative to what?'); the new names align with the existing 'primary/secondary' terminology used throughout the assert_all rollout and follow the Rust Vec<Foo>/foos plural-of-singular convention. Also marks the field with #[serde(default, skip_serializing_if = 'Vec::is_empty')] so it is omitted from JSON output for any test that has no secondary failure data — plain unit tests, fuzz tests, passing tests. Pre-PR JSON consumers continue to see the same shape on those results. invariant_failure_dir and assert_all_invariant_count already had Option::is_none guards. Updates the SimpleContractTest{NonVerbose,Verbose}.json fixtures to drop the now-skipped empty field. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019dce2d-57c7-734a-bbc6-6fa5e34b25de * test(invariant): assert_all + fail_on_revert=false attributes assert() to all live invariants Amp-Thread-ID: https://ampcode.com/threads/T-019dd262-ed81-723c-aaaa-8e1314bed45a Co-authored-by: Amp <amp@ampcode.com> * fix(clippy): use values() instead of iter() with unused key Amp-Thread-ID: https://ampcode.com/threads/T-019df149-03af-722b-abda-d8ab6332ee3b Co-authored-by: Amp <amp@ampcode.com> * fix(clippy): drop redundant references in trimmed_hex format args Amp-Thread-ID: https://ampcode.com/threads/T-019df149-03af-722b-abda-d8ab6332ee3b Co-authored-by: Amp <amp@ampcode.com> * Update crates/evm/evm/src/executors/invariant/error.rs Co-authored-by: stevencartavia <112043913+stevencartavia@users.noreply.github.com> * invariant: unify primary/secondary as one list and one failure type The "anchor" of an invariant campaign is the test entry point selected by `--mt` (or the per-`Test` invariant function the runner is currently exercising). Under `assert_all`, the anchor is the campaign's named test, and any other broken `invariant_*` functions are secondaries shrunk and reported alongside it. - InvariantContract: single invariant_fns list in declaration order with an anchor_idx pointing at the campaign's anchor invariant - TestResult: replace primary/secondary split with invariant_failures: Vec<InvariantFailure>; each entry carries is_anchor so the renderer can omit the function name suffix when a single failure is the anchor (its name is already on the trailing summary line) - assert_invariants/can_continue/assert_after_invariant return the broken invariant directly, removing the first_broken_event re-scan - collapse FailedInvariantCaseData::new + with_assertion_failure into InvariantRunCtx::failed_case - show invariant name on [FAIL: ...] line when not anchor or multiple failures (so secondaries in single-failure assert_all runs are still visible) * invariant: validate signatures upstream and reject parameterized invariants --------- Co-authored-by: Amp <amp@ampcode.com> Co-authored-by: George Niculae <george@gxn3ql7y5j.tail388b2e.ts.net> Co-authored-by: stevencartavia <112043913+stevencartavia@users.noreply.github.com> * feat(forge): add noop --no-commit flag to forge install and forge clone for backwards compatibility (foundry-rs#14689) * feat(forge): add noop --no-commit flag to forge install and forge clone for backwards compatibility `forge install` and `forge clone` no longer commit by default (commit is opt-in via `--commit`). Many AI tools and scripts still pass `--no-commit`, causing an unrecognized flag error. This adds a hidden, noop `--no-commit` flag so those invocations continue to work. Follow-up to foundry-rs#14649 which did the same for `forge init`. Amp-Thread-ID: https://ampcode.com/threads/T-019e15aa-9de3-77a6-9365-21ea300cd785 * test(forge): add test for noop --no-commit flag on forge clone Amp-Thread-ID: https://ampcode.com/threads/T-019e15aa-9de3-77a6-9365-21ea300cd785 --------- Co-authored-by: Centaur AI <ai@centaur.local> Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com> * chore(deps): bump alloy-eip7928 0.3.5 -> 0.3.7 (foundry-rs#14693) Upstream reth (paradigmxyz/reth) now requires alloy-eip7928 ^0.3.6 (since commit d985041). The lockfile here still pinned 0.3.5, which causes resolution failures for any downstream that patches Foundry to use a recent reth revision. Bump the transitive dep to 0.3.7 (latest compatible) so the lockfile stays resolvable. Amp-Thread-ID: https://ampcode.com/threads/T-019e1699-eb69-75aa-afdc-c66246d2f217 Co-authored-by: Centaur AI <ai@centaur.local> * Update flake.lock (foundry-rs#14682) flake.lock: Update Flake lock file updates: • Updated input 'fenix': 'github:nix-community/fenix/74c1591' (2026-05-02) → 'github:nix-community/fenix/f54d645' (2026-05-09) • Updated input 'fenix/rust-analyzer-src': 'github:rust-lang/rust-analyzer/64cdaeb' (2026-05-01) → 'github:rust-lang/rust-analyzer/73ca1d4' (2026-05-08) • Updated input 'nixpkgs': 'github:NixOS/nixpkgs/c6d6588' (2026-05-01) → 'github:NixOS/nixpkgs/b3da656' (2026-05-08) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> * fix: map Optimism Osaka to Karst (foundry-rs#14695) * feat(lint): add missing-inheritance lint (foundry-rs#14661) * feat(lint): add missing-inheritance lint * fix(lint): consider dependency interfaces as candidates for missing-inheritance * fix(script): treat unknown tx as dropped to avoid receipt-poll hang (foundry-rs#14626) * fix(script): treat unknown tx as dropped to avoid receipt-poll hang `provider.get_transaction_by_hash(hash)` returns `Result<Option<Tx>, _>`. `check_tx_status` matched `Ok(_)` for the 'node knows the tx' path, incorrectly bucketing `Ok(None)` (tx unknown) as known. In the `get_receipt`-error branch this fed `RetryError::Continue`, which is unbounded — producing an infinite `eth_blockNumber` + `eth_getTransactionReceipt` loop whenever a tx was rejected at submission or dropped from the mempool after a halt (e.g. anvil's new -32003 mapping for non-REVERT EVM halts). Distinguish `Ok(Some(_))` from `Ok(None)`; treat the latter the same as a transport error and terminate as `TxStatus::Dropped`. Amp-Thread-ID: https://ampcode.com/threads/T-019dfe94-2b0d-71bc-a863-633e05594581 Co-authored-by: Amp <amp@ampcode.com> * test(script): cover check_tx_status dropped/unknown tx paths Amp-Thread-ID: https://ampcode.com/threads/T-019e0814-2cda-7271-a8d6-c59e6739946b Co-authored-by: Amp <amp@ampcode.com> --------- Co-authored-by: Amp <amp@ampcode.com> Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com> Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com> --------- Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com> Co-authored-by: Centaur AI <ai@centaur.local> Co-authored-by: stevencartavia <112043913+stevencartavia@users.noreply.github.com> Co-authored-by: zerosnacks <95942363+zerosnacks@users.noreply.github.com> Co-authored-by: Amp <amp@ampcode.com> Co-authored-by: Mablr <59505383+mablr@users.noreply.github.com> Co-authored-by: grandizzy <38490174+grandizzy@users.noreply.github.com> Co-authored-by: George Niculae <george@gxn3ql7y5j.tail388b2e.ts.net> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Perico Perica <pericc.periccca@gmail.com>
Bumps the actions-weekly group with 1 update in the / directory: [apisec-inc/apisec-run-scan](https://github.com/apisec-inc/apisec-run-scan). Updates `apisec-inc/apisec-run-scan` from 1.0.6 to 1.0.7 - [Release notes](https://github.com/apisec-inc/apisec-run-scan/releases) - [Commits](apisec-inc/apisec-run-scan@0254320...8f66ce9) --- updated-dependencies: - dependency-name: apisec-inc/apisec-run-scan dependency-version: 1.0.7 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions-weekly ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5 to 6. - [Release notes](https://github.com/docker/metadata-action/releases) - [Commits](docker/metadata-action@v5...v6) --- updated-dependencies: - dependency-name: docker/metadata-action dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Deployment failed with the following error: Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Author
|
Looks like docker/metadata-action is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/github_actions/docker/metadata-action-6
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps docker/metadata-action from 5 to 6.
Release notes
Sourced from docker/metadata-action's releases.
... (truncated)
Commits
030e881Merge pull request #607 from crazy-max/allow-comments4b529acchore: update generated contentb0082b3preserve comments in list input values with commentNoInfix7b19fecMerge pull request #604 from docker/dependabot/npm_and_yarn/docker/actions-to...281c9b0chore: update generated content5f43b3btest: stabilize github mock setup since ESM9d53276github class moved since actions-toolkit v0.77.0eaa3d39chore(deps): Bump@docker/actions-toolkitfrom 0.68.0 to 0.77.06b695f7Merge pull request #605 from crazy-max/node24a1afadcnode 24 as default runtimeDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)