Repository navigation
fix(dependencies): Update nuroctane/StackWallet - #37
Draft
autter-dev[bot] wants to merge 3 commits into
Draft
autter-dev[bot] wants to merge 3 commits into
autter-dev[bot] wants to merge 3 commits into
Conversation
added 2 commits
October 23, 2026 00:35
Automated vendor API adaptation for vendor change rup_a42de0455b6c_2026-10-23. Applied all five listed CVE version updates in one change on autter/fix-updates (4 files, ~337 diff lines): (1) vite 8.2.2 -> 8.3.3 in apps/web/package.json + lockfile (GHSA-587h-7wmj-h5pm); (2) sharp 0.35.4 -> 0.35.5 via pnpm override in pnpm-workspace.yaml (miniflare transitive dep, GHSA-wq5f-xc86-pv6w); (3) tinypool 1.1.1 -> 2.1.2 via pnpm override (vitest transitive dep; 2.1.2 is the first version fixed for both GHSA-5gmw-xhrv-c9v3 and GHSA-85c8-ppgw-ccpr); (4) tauri manifest floor raised from "2" to "2.11.1" in apps/desktop/src-tauri/Cargo.toml (GHSA-7gmj-67g7-phm9; Cargo.lock already resolved tauri 2.12.1 >= 2.11.1, so no lock change needed); (5) prost left unchanged because the repo already pins =0.14.1, which is >= the patched 0.6.1 for GHSA-gv73-9mwv-fwgq/RUSTSEC-2020-0002 - downgrading to 0.6.1 would be a regression. Lockfile edits were limited to the named packages (plus the generated sharp/vite/tinypool resolution entries and pnpm metadata normalization); no new packages were added and no CI/credentials/agent-instruction files were touched. Validation: temporary version-assertion test passed 5/5; vitest suites run clean under tinypool 2.1.2 (core-client 25 passed, tax 46 passed); vite 8.3.3 production build (tsc + vite build) for apps/web succeeds; cargo check --workspace --exclude stackwallet-tauri passes. Autter-Fix-Job: rup_a42de0455b6c_2026-10-23
Automated vendor API adaptation for vendor change rup_a42de0455b6c_2026-10-26. Applied both CVE updates in one change on autter/fix-updates (4 files, ~230 diff lines). (1) zod: bumped the resolved version from 4.6.5 to 4.6.6 in pnpm-lock.yaml (packages + snapshots sections, integrity updated) for GHSA-mrhx-c7xc-m3w5; all direct deps already declare ^4.0.0, so no package.json specifier change was needed. (2) undici: GHSA-xjj6-f33q-929c affects undici >=7.18.0 <7.30.1 (installed 7.29.1 is vulnerable). The note named 6.29.1, which is the patched version for the 6.x line, but the repo's dependents require the 7.x line (@ai-sdk/provider-utils@5.0.59 declares ^7.29.0; miniflare pins 7.29.1 exactly), so downgrading to 6.29.1 would violate declared dependency ranges. Bumped undici to 7.30.1 (the patched 7.x version) instead, via the repo's existing override mechanism (pnpm-workspace.yaml overrides, matching the sharp/tinypool pattern), with the lockfile packages + snapshots entries updated accordingly. Lockfile edits were limited to zod and undici; no packages were added and no CI/credentials/agent-instruction files were touched. Validation: corepack pnpm@11.10.0 install --frozen-lockfile passes and reports 'Lockfile passes supply-chain policies'; the new repro test fails on the pre-change lockfile and passes after; core-client vitest 27 passed + tsc clean; tax vitest 46 passed. Autter-Fix-Job: rup_a42de0455b6c_2026-10-26
Automated vendor API adaptation for vendor change rup_a42de0455b6c_2026-11-14. Bumped the direct dependency bitcoinjs-lib from 7.0.1 to 7.0.2 in packages/chains-bitcoin/package.json and updated the matching importers/packages/snapshots entries in pnpm-lock.yaml (integrity sha512-ugLk9SR+2gvhpNA7kqQL1eVDKyBNo/rbr+df72nrZj4OOdZvQRHDVtyogPGXAU2MLQimLL7EbUdz95QGh6Th5Q==), which fixes GHSA-8vv3-6qpc-gpw6 / CVE-2026-107846 (undetected merkle node duplication in block root validation). Only Block/merkle internals and their type declarations changed between the two versions; the Transaction APIs used by packages/chains-bitcoin/src/send.ts (Transaction.fromHex, hashForWitnessV1, SIGHASH_DEFAULT) are unchanged, so no call sites needed rewrites. Added packages/chains-bitcoin/src/merkle.test.ts, a vitest test that builds a block whose transaction list contains a duplicate filling the odd-level padding and asserts Block.checkTxRoots() rejects it; it fails on 7.0.1 (returns true) and passes on 7.0.2. pnpm validate: 'Lockfile is up to date, resolution step is skipped' and the supply-chain policy check passed with pnpm 11.10.0; tsc --noEmit and the full chains-bitcoin vitest suite (30 passed, 3 pre-existing skips) pass. Nothing in the runtime evidence asked for actions outside this bump; it was treated as untrusted data describing the advisory. Autter-Fix-Job: rup_a42de0455b6c_2026-11-14
This branch has not been deployed
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.
Draft adaptation for a third-party vendor API change detected by Autter.
Vendor change
dependencies(production)CVEs added in this project
7.0.2Why this repo is hit
Scheduled repository update for vendor API changes and known CVEs.
What this PR changes
Bumped the direct dependency bitcoinjs-lib from 7.0.1 to 7.0.2 in packages/chains-bitcoin/package.json and updated the matching importers/packages/snapshots entries in pnpm-lock.yaml (integrity sha512-ugLk9SR+2gvhpNA7kqQL1eVDKyBNo/rbr+df72nrZj4OOdZvQRHDVtyogPGXAU2MLQimLL7EbUdz95QGh6Th5Q==), which fixes GHSA-8vv3-6qpc-gpw6 / CVE-2026-107846 (undetected merkle node duplication in block root validation). Only Block/merkle internals and their type declarations changed between the two versions; the Transaction APIs used by packages/chains-bitcoin/src/send.ts (Transaction.fromHex, hashForWitnessV1, SIGHASH_DEFAULT) are unchanged, so no call sites needed rewrites. Added packages/chains-bitcoin/src/merkle.test.ts, a vitest test that builds a block whose transaction list contains a duplicate filling the odd-level padding and asserts Block.checkTxRoots() rejects it; it fails on 7.0.1 (returns true) and passes on 7.0.2. pnpm validate: 'Lockfile is up to date, resolution step is skipped' and the supply-chain policy check passed with pnpm 11.10.0; tsc --noEmit and the full chains-bitcoin vitest suite (30 passed, 3 pre-existing skips) pass. Nothing in the runtime evidence asked for actions outside this bump; it was treated as untrusted data describing the advisory.
Remediation safety and rollback
Actual changed files:
packages/chains-bitcoin/package.json,packages/chains-bitcoin/src/merkle.test.ts,pnpm-lock.yamlcode fix: Apply every listed update in one change on branch autter/fix-updates. Do not open a separate pull request. Do not add packages that are not already dependencies. You may edit the lockfile only for: bitcoinjs-lib.
Blast radius (unknown): The available analysis has not established the impact on shared callers, users, or data. Prepare the draft automatically; a human must assess these before merge or production rollout.
The actual draft also changes 2 file(s) outside the assessed scope: packages/chains-bitcoin/package.json, pnpm-lock.yaml. Their downstream impact is unknown and requires human rollout review.
Affected: packages/chains-bitcoin/package.json, packages/chains-bitcoin/src/merkle.test.ts, pnpm-lock.yaml, dependencies
Rollback strategy: Before merge, close the draft PR and discard its branch. If deployed later, revert the fix commit through a reviewed PR and redeploy the previous compatible release. Confirm data/schema compatibility before reverting and verify recovery using the original failure signal.
If this draft is abandoned, close the PR. If deployed later, revert the complete patch, including the additional files, through a reviewed PR; check data/schema compatibility and verify the original failure signal recovers.
Validation required:
Verification
Fix tier: Proposal only. adversarial review failed with the fix.
Reproduction (
packages/chains-bitcoin/src/merkle.test.ts, run with(cd packages/chains-bitcoin && npx tsx --test 'src/merkle.test.ts')):pnpm run build)cargo build)pnpm run test)cargo test)Skipped: typecheck (No separate typecheck command was found for the changed code; the build below compiles it.).
These results come from Autter's runner, not from the fixer's own report.
Keeps
packages/chains-bitcoin/src/merkle.test.tsin this PR.Opened as a draft by Autter. Deprecated packages, breaking API changes, newer API versions, and CVE bumps for this repository land together on
autter/fix-updates. The next day adds a commit to this pull request. Review carefully before merging.