Sweep dependencies and bump to 2.12.1 - #129
Merged
Merged
Conversation
Takes @agent-score/sdk 2.7.11 (the one runtime dependency), moves the coupled mppx and viem pins to 0.9.3 and 2.56.5 (the Tempo proof domain stays at version 3), moves the osv-scanner binary to v2.6.0, and fixes the stale linked-sdk note in CLAUDE.md.
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.
Summary
Dependency sweep for node-commerce, plus the release bump to 2.12.1.
@agent-score/sdkfloor^2.7.10to^2.7.11, the release published earlier in this sweep. It is the package's one runtime dependency, so merchants installing 2.12.1 get it.mppx0.9.2 to 0.9.3 andviem2.56.3 to 2.56.5, in both the dev pin and the single-versionviemoverride. The Tempo zero-amount proof EIP-712 domain indist/tempo/internal/proof.jsis still version'3'in 0.9.3, so agent and verifier cannot disagree on it. The 0.9.3 changes on this package's import path (mppx/server, rootmppx) are additive: challenge context on payment-success hooks, a fee-payer policy option that allows sponsorship by default, Stripe PaymentIntent metadata, and patchedfast-uri/qs. mppx 0.9.3's peers (viem >=2.54.0,@x402/core >=2.22.0,hono >=4.12.25,express >=5) all resolve satisfied, and the lock holds one viem copy.link:@agent-score/sdk; it has been a registry range, so the note now says how to link temporarily and restore.@solana/kit8.3.0,fastify5.12.4 and dev tooling into the lock.Override drill, each removed alone from a clean install:
axios ^1.18.0is load-bearing (cdp-sdk's exact 1.16.0 returns without it),esbuild ^0.28.1is load-bearing (0.27.7 returns),viemresolves identically without it today and stays as the coupled set's single-version discipline.Checked and found current:
@x402/core/evm/extensions2.25.0 and@solana/mpp0.7.0 are upstream latest (exact pins, whichbun outdatedcannot show); every Action is on its latest release-tag major; bun 1.4.2; dependabot config (held majors scoped, coupled pins blanket-ignored by design); hook/CI parity. A nested@solana/kit5.5.1 under dev-only@coinbase/cdp-sdkpredates this change.Not taken: eslint 10 and TypeScript 7 (org-wide holds), lefthook 2.1.14 (inside the 24h release-age soak).
Still owed, and sequenced rather than dropped: the holds registry requires a live Base, Tempo and Solana settle after a coupled-set bump. It needs pay on mppx 0.9.3 paying a storefront running 2.12.1, so it runs at the storefront stage of this sweep.
Type of change
Public API
None. No exported type, signature, or wire shape changed.
Test plan
From a clean
bun install --frozen-lockfile:bun run lint,bun run build,bun run typecheck(source and examples),bun run knip,bun run testwith coverage (119 files, 1825 passed, 4 skipped), all exit 0.osv-scanner2.6.0 overbun.lock: 899 packages, no issues.Checklist
Worked with Varun. The tag follows the merge.