chore: refresh sibling package pins; bump to 3.3.1:5#55
Closed
helix-nine wants to merge 1 commit into
Closed
Conversation
npm install + npm update: - bitcoin-core-startos pin c745e4d → 132f3e7 (next/28.x HEAD) - lnd-startos pin 0e166a0 → 0999634 (next HEAD) - nested @start9labs/start-sdk 1.5.0 → 1.5.1 (matches package.json pin) Rename v3.3.1_4.ts → v3.3.1_5.ts in place per packaging convention (no migration change; the Low-CPU profile bootstrap migration carries forward unchanged for users still on v3.3.1:3).
Member
|
Closing — this PR was opened by an early/stale-code update-monitor run. The change is either already on master or not a real upstream bump (SDK/dep refresh). A fresh run on current code will re-open if still warranted. |
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
2 participants
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
Routine maintenance pass. SDK is already at 1.5.1 and upstream Mempool is at the latest v3.3.1, so this PR is just the dependency refresh:
bitcoin-core-startospinc745e4d→132f3e7(currentnext/28.xHEAD)lnd-startospin0e166a0→0999634(currentnextHEAD)@start9labs/start-sdkin lockfile1.5.0→1.5.1(matches thepackage.jsonpin that landed in chore: bump start-sdk to 1.5.0; refresh dep refs #54)cln-startoswas already atnextHEAD; no change.Renamed
startos/versions/v3.3.1_4.ts→v3.3.1_5.tsin place per the packaging convention (no new migration; the Low-CPU profile bootstrap migration shipped at:4carries forward unchanged so users still on3.3.1:3get migrated correctly).Test plan
npm run check(typecheck) passesmakebuilds both x86_64 and aarch64.s9pkcleanly (v3.3.1:5, SDK1.5.1)3.3.1:3and3.3.1:4succeeds