Repository navigation
Maintenance sweep: mppx 0.13.4, Node 26 support, release 3.1.1 - #154
Merged
Merged
Conversation
Move the payment set to mppx 0.13.4 and viem 2.57.4 (mppx 0.13.2 fixes a tempo/charge replay-marker release that let a settled transaction pass replay protection again). Widen engines.node to >=22 <27 with a CI job testing Node 22, 24 and 26. Bump lefthook and bun, and drop the proxy-addr, smol-toml and source-map-js overrides, which a fresh resolution no longer needs.
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.
Summary
tempo/chargeno longer releases another request's replay marker when a transaction's final hash collides with an already-claimed one, which previously let a settled transaction pass replay protection again.dist/tempo/internal/proof.jsis byte-identical between the two versions (domain version 3).engines.nodewidens to>=22 <27. A newnode-compatjob builds and runs the suite on Node 22, 24 and 26.packageManagerbun 1.4.3.proxy-addr,smol-tomlandsource-map-jsoverrides: removing them against the existing lock changes nothing, and a fresh resolution keeps all three at the old floors (proxy-addr 2.0.8, smol-toml 1.9.0, source-map-js 1.2.2).axios(1.16.0 under cdp-sdk without it),esbuild(0.27.7 without it) and the exactviemoverride stay.Worked with Varun.
Not taken: eslint 10 and TypeScript 7 stay held.
@agent-score/sdk2.9.1 lands as a follow-up commit once it publishes.Still owed: a live settle on Base, Tempo and Solana once the storefronts carry this set. It will be recorded on the pay PR.
Type of change
Public API
None.
Test plan
Locally: lint, build, typecheck, knip and test (1636 passed, 4 skipped) all exit 0, and the suite passes under Node 22.23.2, 24.21.0 and 26.11.1. The existing test that decodes a real Tempo challenge still pins a single USDC offer under 0.13.4. OSV scan clean.
Checklist