Build Service / BuildPackage (push) Canceled after 0s
Wrapper-only revision: the images are unchanged from 0.2.1:0, so only the downstream digit moves. Release notes now describe this revision (rebuilt against start-sdk 2.0.9, requires StartOS 0.4.0-beta.10) instead of 0.2.1:0's image bumps. The version file moves to versions/current.ts, where the guide keeps the latest version — a dated file is only for a released version that carries a migration, and this bump carries none. No `other` entry is needed: the version graph synthesizes a range beneath current, and the packed manifest derives canMigrateFrom <=0.2.1:1. Co-authored-by: Cursor <cursoragent@cursor.com>
1.6 KiB
1.6 KiB
TODO — bring Spaces from beta.9 to beta.10
Consult the packaging guide as you go
(start-technologies/projects/start-sdk/docs/src/recipes.md is the intent index). Remove items as you finish
them, and add items when you defer work.
Docs
- Write
README.md(perstart-technologies/projects/start-sdk/docs/src/writing-readmes.md). - Write
instructions.md(perstart-technologies/projects/start-sdk/docs/src/writing-instructions.md). - Fill in
UPDATING.md(upstream-version tracking).
Build, test, ship
- Build for arm (
ARCHES := x86 armin theMakefile). All four images declareaarch64in the manifest and every tag publishes an arm64 variant, so the package currently advertises support it never ships. Needs an arm box to verify. - First test build:
make(orstart-cli s9pk pack); fix anytsc/ pack errors. - Install on a StartOS box and verify the service runs — done for 0.2.1:0 on
natural-dean.local: all daemons up, nacho's
EXPO_PUBLIC_API_BASE_URLresolved through the subs-api host rather than the loopback fallback. - Verify the Bitcoin RPC task on a fresh install (
accept/setinput under SDK 2.0).taskBtcAuthreturns early whenstore.btcAuthexists, so an update over an existing install never exercises it. npx prettier --write startos— 9 files predate the current prettier config and fail--check(untouched by the SDK bump, so left out of that diff).- Backup / restore sanity check.
- Review the README and instructions one more time against actual behavior.