chore: bump @start9labs/start-sdk to 1.5.0#73
Closed
helix-nine wants to merge 1 commit into
Closed
Conversation
Pure dependency bump (1.3.3 → 1.5.0). `tsc --noEmit` clean, `make` produces both x86_64 and aarch64 .s9pk artifacts. No source changes required; no version bump (precedent: 572affc).
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
1.3.3→1.5.0. Clean update —tsc --noEmitpasses with no changes to package source.npm updateto refresh transitive deps.No StartOS version bump (matches precedent set by 572affc, which bumped 1.3.2 → 1.3.3 without touching
startos/versions/). Synapse (1.152.1) and Ketesa (v1.2.1) are already on the latest upstream releases.Verification
npx tsc --noEmit— clean.make— bothsynapse_x86_64.s9pk(192M) andsynapse_aarch64.s9pk(180M) build successfully;SDK: 1.5.0reported in the build banner.Test plan