- Pull request
The fix is in.
Can you ship it?
Patchdesk helps developers decide when to adopt an open-source fix. See what changed, which tests passed, and what to try in your own app.
Your tracked fixesSwitch to native fetch
One HTTP client changed.
The Safe API kit replaced node-fetch with the runtime’s built-in fetch. If your service reads Safe transactions, the request now depends on the fetch implementation in your runtime.
A Node 24 run failed on v1.3.0. Compare the run’s dependency versions with your lockfile.
Replay one read-only request.
Run the same Safe transaction lookup on Node 24 with your current SDK and with the candidate commit. Compare the response for a known transaction, then try an invalid ID and compare the errors.
Try a release decisionYour tracked fixes.
Check your own fix.
Bring a public pull request to see the checks on its commit.
Make the release call.
Choose how you would handle a real pull request. Compare your decision with the recorded checks, then take a test plan back to your project.
Gas estimates now use the latest block.
Retest fee estimation with your own chain hook against merge commit 9381167d.
Public repair records
GitHub snapshots from 20 Nov 2026
Check how the Safe API client handles requests in your runtime.
Review a change to the way a wallet client resolves its chain.
Inspect the checks behind a command-line library update.
Trace a package release.
Enter the npm version from your lockfile to see the runtime dependencies it declares. Expand the result to inspect each version requirement.
Review a Sentry issue alongside the releasePrice a delivery bond.
Try the operator lab’s Node 22 date repair at $80 per platform. Broader test coverage raises the practice PATCH commitment. An underwriter can cover part of that bond.
Total delivery bond
20 PATCH- Operator
- 10 PATCH
- Underwriter
- 10 PATCH
- Maximum operator loss
- 5 PATCH