Skip to content

chore: bump start-sdk to 1.5.2; 28.4:11 → 28.4:12#216

Closed
helix-nine wants to merge 1 commit into
28.xfrom
next/28.x
Closed

chore: bump start-sdk to 1.5.2; 28.4:11 → 28.4:12#216
helix-nine wants to merge 1 commit into
28.xfrom
next/28.x

Conversation

@helix-nine
Copy link
Copy Markdown
Contributor

Summary

  • start-sdk 1.5.1 → 1.5.2; version file renamed in place from v28.4.11.tsv28.4.12.ts (no migration).
  • Bitcoin Core stays at 28.4 — already the latest release on the 28.x line.
  • npm update to refresh transitive deps.

1.5.2 is a single bug-fix: Backups.withPgDump / withMysqlDump now stage the dump file in /tmp and cp it through the FUSE backup mount, instead of writing directly (where pg_dump/mysqldump's writes were silently truncated to 0 bytes). bitcoin-core-startos uses neither helper, so this is an internal SDK refresh with no runtime impact on this package — release notes flag it as **Internal**.

Test plan

  • make produces bitcoind_{x86_64,aarch64,riscv64}.s9pk (28.4:12, SDK 1.5.2).
  • Sideload one arch and confirm bitcoind starts cleanly and reports 28.4.

- start-sdk 1.5.1 → 1.5.2; version file renamed in place
  from v28.4.11.ts → v28.4.12.ts (no migration in this bump).
- npm update to refresh transitive dependencies.

1.5.2 fixes Backups.withPgDump / withMysqlDump (database dumps were
silently truncated to 0 bytes when written through the backup-fs FUSE
mount). bitcoin-core-startos doesn't use either helper, so this is an
internal SDK refresh with no runtime impact on this package.

Upstream Bitcoin Core 28.x: already at 28.4 (latest on the 28.x line).
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.

2 participants