Repository navigation
chore(deps): Bump the npm-maintenance group across 1 directory with 2 updates - #52
Merged
Merged
Conversation
dependabot
Bot
added
dependencies
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/npm-maintenance-4249701cd3
branch
from
November 11, 2026 08:35
eff5b43 to
b513f9e
Compare
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
I re-reviewed the regenerated lockfile and found no bugs. A human should still look before merging, because the viem bump runs under the deployment signer guard and the vitest graph is now mixed.
What was reviewed:
- The catalog,
overridesand lockfile entries for viem 2.57.16 and vitest 5.1.0 line up. The new integrity hashes are present. deployments/modules/signer.ts(guardedTransactionRequest/assertSigningIntent) rejects any prepared transaction that setsvalidAfteror changesvalidBefore/nonceKey. viem 2.57.15 changed how Tempo expiring nonces fillvalidAfter/validBefore. The guard pinsnonceKey: 0n, so it should not be affected, but viem was not installed here and I could not confirm that from viem's source.- vitest 5.1.0 now resolves its optional peers to
@ vitest/uiand@ vitest/browser-previewat 5.0.5, while vite-plus 1.3.0 still brings in vitest 5.0.5. The plainvitesttest scripts should not load either package, but pnpm will likely warn about the unmet peers. - Not done: no install, typecheck or test run, so
signer.test.tswas not run against the new viem.
Extended reasoning...
This is a dependency bump that touches only pnpm-workspace.yaml and pnpm-lock.yaml: viem goes from 2.57.14 to 2.57.16 and vitest from 5.0.5 to 5.1.0. No source files change. The deployments package signs authority transactions through viem's Tempo preparation and relies on a strict intent guard. The viem releases in this range change Tempo expiring-nonce and CCIP behaviour, so a viem bump can affect that signing path. Since no tests ran and the lockfile now has vitest 5.1.0 paired with 5.0.5 companion packages, I am deferring to a human rather than approving.
… updates Bumps the npm-maintenance group with 2 updates in the / directory: [viem](https://github.com/wevm/viem) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `viem` from 2.57.14 to 2.57.16 - [Release notes](https://github.com/wevm/viem/releases) - [Commits](https://github.com/wevm/viem/compare/viem@2.57.14...viem@2.57.16) Updates `vitest` from 5.0.5 to 5.1.0 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.1.0/packages/vitest) --- updated-dependencies: - dependency-name: viem dependency-version: 2.57.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-maintenance - dependency-name: vitest dependency-version: 5.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-maintenance ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/npm-maintenance-4249701cd3
branch
from
November 12, 2026 08:35
b513f9e to
7055ee8
Compare
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
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 the npm-maintenance group with 2 updates in the / directory: viem and vitest.
Updates
viemfrom 2.57.14 to 2.57.16Release notes
Sourced from viem's releases.
... (truncated)
Commits
98aa491chore: raiseviem/enssize limit (#5398)71241b2chore: version package (#5393)e1329c9fix(tempo): check Gateway chain and refresh balances before payment errors (#...c60ca26feat(tempo): fund-aware Gateway payments and InsufficientFundsError (#5395)264ab41docs(tempo): use code groups with viem.config in Gateway guides (#5394)721d682feat(tempo): add experimental Gateway actions (#5391)9348d38perf: skip retries for method refusals and trim per-request overhead (#5392)5711b7echore: version package (#5363)dbf8ae6test: stabilizesendTransactionSynctimeout andwatchBlockscatch-up test...141f8c0feat(tempo): add Account.serialize, Account.deserialize and keyAuthorization ...Updates
vitestfrom 5.0.5 to 5.1.0Release notes
Sourced from vitest's releases.
... (truncated)
Commits
7a38449chore: release v5.1.0 (#11838)a5ec316fix(vm): keep assignable accessor globals writable in node environment (#11834)e46c6c1refactor: share trace types and utils (#11825)9e23ce5refactor(snapshot): unify review update withSnapshotStateupdate (#11790)a0e33ccchore: eliminate lint error (#11822)fd145d8feat(experimental): add message option to vi.waitFor and vi.waitUntil (#11754)4e98551feat(experimental): add trace timeline for node (#11753)bf96dadfix: preserve rootDir in project paths (#11816)54e5b8afeat: interactively review failed snapshots (#11325)4277075fix(expect): keep soft .resolves/.rejects error location (#11792)