Skip to content

chore: bump @start9labs/start-sdk to 1.5.1 - #6

Open
helix-nine wants to merge 1 commit into
dathonohm:bip110-startos0.4.0from
helix-nine:helix/task-5-sdk-bump
Open

chore: bump @start9labs/start-sdk to 1.5.1#6
helix-nine wants to merge 1 commit into
dathonohm:bip110-startos0.4.0from
helix-nine:helix/task-5-sdk-bump

Conversation

@helix-nine

Copy link
Copy Markdown

Summary

  • Bumps @start9labs/start-sdk from 1.0.01.5.1.
  • Adds overrides.@start9labs/start-sdk to package.json so npm hoists a single SDK copy across the sibling Start9 deps (bitcoin-core-startos, bitcoind-knots, tor-startos) which still pin older SDK versions. Without this override, two SDK copies cause TS to infer generic input types as never in helpers like sdk.action.createTask.
  • Renames startos/versions/v29.3_2.tsv29.3_3.ts, bumps the package revision to #knotsrdts:29.3:3, and updates release notes (rename-in-place per the migration-free bump convention).

Upstream check

  • Bitcoin submodule is pinned at v29.3.knots20260210+bip110-v0.4.1 (78dfa44a). This is the latest BIP-110 tag in dathonohm/bitcoin. Newer Bitcoin Knots tags (v29.3.knots20260507, v29.3.knots20260508) exist, but the BIP-110 patches haven't been rebased onto them yet — no submodule bump in this PR.
  • bip110/knots-rebase-20261212 describes as v29.2.knots20251110-62-…, i.e. older than the current pin, not a forward rebase.

What npm update was scoped to

npm update was intentionally limited to the SDK bump (lockfile reverted for git-pinned deps). Pulling the current tips of bitcoin-core-startos#30.x and bitcoind-knots#next would remove the v28.3.5 / v29.3.5 / v30.2.5 Core version files this package — and Retropex/knots-startos#next itself — still import, breaking typecheck across the board:

node_modules/bitcoind-knots/startos/versions/index.ts(2,38): error TS2307:
  Cannot find module 'bitcoin-core-startos/startos/versions/v28.3.5'
…

Resolving that requires updating Core/Knots cross-version references (satisfies, the migrations.other keys, the versionGraph.other array) in tandem with an upstream Retropex bump that's outside the scope of a routine SDK refresh — flagging here so it can be picked up in normal development.

Test plan

  • npm install succeeds with the new SDK pinned at 1.5.1 and overridden across deps (npm ls @start9labs/start-sdk shows a single deduped copy).
  • npm run check (tsc) passes.
  • npm run build (ncc bundle) succeeds.
  • make produces an .s9pk (the Makefile expects .git/HEAD/.git/index directly in the worktree, which doesn't exist in a git worktree checkout — pre-existing limitation of this repo's s9pk.mk, not introduced by this PR; the hello-world-synced version from bitcoin-core-startos resolves it via git rev-parse).

Adds an `overrides` entry to force a single hoisted SDK copy across the
sibling Start9 package dependencies (bitcoin-core-startos, bitcoind-knots,
tor-startos), which still pin older SDK versions.

Renames v29.3_2.ts → v29.3_3.ts and bumps the package revision to
`#knotsrdts:29.3:3` per the rename-in-place convention for migration-free
bumps.

`npm update` was intentionally limited to the SDK bump: pulling the
current tips of `bitcoin-core-startos#30.x` and `bitcoind-knots#next`
removes the v28.3.5 / v29.3.5 / v30.2.5 Core version files this package
(and Retropex's `next`) still import, breaking typecheck. Resolving that
requires updating Core/Knots cross-version references in tandem with
upstream Retropex — out of scope for a routine SDK bump.

Typecheck (`npm run check`) and bundle (`npm run build`) both pass.
@dathonohm

Copy link
Copy Markdown
Owner

@Retropex can comment here, but my guess is that the official Knots package is what you want here, since BIP-110 is now merged into Knots v29.3.knots20260508.

@Retropex

Copy link
Copy Markdown
Collaborator

Correct, the latest version of Knots now include BIP 110. There is no need to maintain this package anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants