chore: migrate to start-sdk 2.0 and bump SimpleX Chat to 6.5.5#7
Open
helix-nine wants to merge 5 commits into
Open
chore: migrate to start-sdk 2.0 and bump SimpleX Chat to 6.5.5#7helix-nine wants to merge 5 commits into
helix-nine wants to merge 5 commits into
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F5qZh4QiVySBLkV5ya7XSr
helix-nine
changed the title
Bumps @start9labs/start-sdk 2.0.1 -> 2.0.3 (dependency and lockfile only). - 2.0.3 fixes a dependency-gated daemon wedging permanently after its dependency's readiness flaps: Daemon.term() unconditionally destroyed the daemon's SubContainer, so the next start() threw "already destroyed" and the daemon never recovered. Adds a non-destroying Daemon.stop() for dependency-driven pauses, and serializes pause/resume transitions. - 2.0.2 runs s9pk.mk's check-deps before packing, not just before install. No packaging API changed between 2.0.1 and 2.0.3, so no source changes were needed. Verified with `npm run check` (tsc --noEmit).
Bumps @start9labs/start-sdk 2.0.3 -> 2.0.5 (dependency and lockfile only). 2.0.5 fixes ExVer range operations ignoring the downstream revision: compareVersionRangePoints and adjacentVersionRangePoints compared the upstream twice, so two points sharing an upstream but differing downstream (1.0.0:3 vs 1.0.0:15) collapsed into one. normalize() then dropped the lower of the two, which made packed manifests advertise a canMigrateFrom/canMigrateTo range narrower than the truth for any package whose `other` versions share current's upstream. No upgrade path actually broke — StartOS resolves migrations through the version graph rather than this field — but the manifests were wrong. No packaging API changed, so no source changes were needed. Verified with `npm run check` (tsc --noEmit).
Two naming mismatches, one of them a silent data-path bug.
1. The image and its source repo were renamed upstream (image revision 6.5.5-2):
lundog/simplex-chat -> lundog/simplex-websocket-bridge, and
lundog/simplex-chat-docker -> lundog/simplex-websocket-bridge-docker. The
GitHub repo redirects; the old Docker Hub repo does NOT — it is frozen at
6.5.5-1 and gets no further builds. Repointed the pin to
lundog/simplex-websocket-bridge:6.5.5-2.
Verified 6.5.5 -> 6.5.5-2 is functionally a no-op for the running container:
across that range the entrypoint changed only three echoed log strings, the
Dockerfile changed only an OCI label, and the image configs (HOME, entrypoint,
workdir, user) are byte-identical. Note the new repo's unsuffixed `6.5.5` tag
is the -2 build, NOT the same digest as the old repo's `6.5.5` — so the
explicit revision is pinned to stop the tag shifting underneath us.
2. The file-exchange contract was broken by the 6.5.5 bump and would have shipped.
The bridge takes its inbound/temp dirs from SIMPLEX_INBOUND_DIR /
SIMPLEX_TMP_DIR, which this package never set — it relied on the image's
defaults. Through image 6.5.4 those defaulted to /simplex/{inbound,tmp}, which
is exactly where our `/simplex` mount (the volume's .simplex/media subpath)
expects them. Image 6.5.5's "file/profile config rework" changed the defaults
to $HOME/.simplex/{files,tmp} — outside that mount.
So on 6.5.5 the bridge writes received files to .simplex/files while /simplex
points at .simplex/media, which it never touches. A consumer mounting
.simplex/media/inbound sees an empty directory, and nothing errors. main.ts now
passes both variables explicitly (/simplex/inbound, /simplex/tmp), restoring
the 6.5.4 paths — so no data moves and no migration is needed. inbound and tmp
stay siblings in one mount, preserving the atomic temp->files rename (separate
mounts would EXDEV-fail).
This only ever affected 0.2.1:0, which is unreleased (alpha, beta and prod all
carry 0.2.0:0 on image 6.5.4), so 0.2.1:0 is amended in place rather than
superseded.
Also records both traps in UPDATING.md — bump from the image tag list rather than
the SimpleX release list, and re-check the image's file-exchange defaults on every
bump — and refreshes the stale image names in README.
Verified with `npm run check` (tsc --noEmit); the new tag resolves via
`docker manifest inspect`.
Note: startos/actions/api-keys.ts has pre-existing prettier drift, untouched here.
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
1 participant
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.
start-sdk 2.0 migration + SimpleX Chat 6.5.5
Migrates this package to
@start9labs/start-sdk2.0 (requires StartOS 0.4.0-beta.10) and bumps the bundled SimpleX Chat client from 6.5.4 to 6.5.5. Package version0.2.0:1→0.2.1:0.start-sdk 2.0 migration
2.0.1, TypeScript →^6,tsconfig.jsonextends the shippedtsconfig.base.json,Makefileincludes the SDK'ss9pk.mk(vendored copy removed), reusable CI workflows repointed toStart9Labs/start-technologies.sdk.serviceInterface.*→sdk.host.*resolved over the LXC bridge, lazySubContainer,alertsmanifest field removed, and other### Changed/### Removeditems from the SDK 2.0 changelog.Upstream bump — SimpleX Chat 6.5.5
images.simplex.source.dockerTag→lundog/simplex-chat:6.5.5(multi-arch amd64 + arm64 confirmed on Docker Hub).startos/versions/current.ts.Test plan
npm ci→tsc→ SDK lint →ncc→s9pk pack).simplex-websocket-bridge_x86_64.s9pkon a StartOS 0.4.0-beta.10 server.0.2.0/0.1.xbuild, then upgrade in place to0.2.1:0; confirm existing profile/data volume (.simplex, media folder) survives and the service restarts healthy.🤖 Generated with Claude Code