Update tests.yml

[Dargon789]

ea7e889

Summary by Sourcery

Simplify and modernize the CI test workflow configuration.

Build:

• Upgrade GitHub Actions to v4 variants in the tests workflow, including in commented coverage configuration.

CI:

• Consolidate multiple per-package test jobs into a single test job that depends on the build, installs Foundry/Anvil, and runs the full test suite after building.
• Adjust the build job to perform a clean before building and document where to find an example of per-package parallel tests.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
sequence-js-web	Error		Jan 7, 2026 2:59pm
sequence.js	Ready	Preview, Comment	Jan 7, 2026 2:59pm
wagmi-project	Ready	Preview, Comment	Jan 7, 2026 2:59pm

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's Guide

Streamlines the CI test workflow by upgrading GitHub Actions to v4, introducing a clean step before builds, consolidating all per-package tests into a single test job that depends on the build, and integrating Foundry/Anvil for tests that require an Arbitrum forked network.

File-Level Changes

Change	Details	Files
Upgrade GitHub Actions versions to v4 for checkout, setup-node, and cache steps.	Update all uses of actions/checkout from v3 to v4 in active jobs Update commented-out coverage job to use actions/checkout@v4, actions/setup-node@v4, and actions/cache@v4	.github/workflows/tests.yml
Simplify and restructure the CI workflow to build once and run a single unified test job.	Adjust build job to run pnpm clean before pnpm build Rename and redefine tests job to depend on the build job instead of install Remove multiple per-package test jobs (0xsequence, abi, account, api, etc.) in favor of a unified tests job that runs pnpm test Add a note referencing the v2 branch for an example of per-package parallel tests	.github/workflows/tests.yml
Integrate Foundry/Anvil into the test job for EVM-based tests against an Arbitrum fork.	Install Foundry using foundry-rs/foundry-toolchain@v1 at version v1.5.0 in the tests job Start an Anvil instance in the background using an Arbitrum fork URL prior to running tests Ensure the tests job runs pnpm build and pnpm test after the Anvil setup	.github/workflows/tests.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

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

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

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

[sourcery-ai]

Hey - I've left some high level feedback:

• The tests job depends on build but still re-runs pnpm build and install-dependencies; consider relying on the build artifacts or caching instead of rebuilding/reinstalling to avoid redundant work.
• The previous workflow ran pnpm typecheck and pnpm lint in the build job, which are now removed; if this is unintentional, you may want to reintroduce them or move them to a separate job so static checks still run in CI.
• Anvil is started in the background without any explicit readiness check; if tests occasionally fail due to the node not being ready in time, consider adding a small wait or a health-check loop before running pnpm test.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `tests` job depends on `build` but still re-runs `pnpm build` and `install-dependencies`; consider relying on the build artifacts or caching instead of rebuilding/reinstalling to avoid redundant work.
- The previous workflow ran `pnpm typecheck` and `pnpm lint` in the `build` job, which are now removed; if this is unintentional, you may want to reintroduce them or move them to a separate job so static checks still run in CI.
- Anvil is started in the background without any explicit readiness check; if tests occasionally fail due to the node not being ready in time, consider adding a small wait or a health-check loop before running `pnpm test`.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}