chore: migrate to start-sdk 2.0#5
Open
helix-nine wants to merge 1 commit into
Open
Conversation
helix-nine
changed the title
helix-nine
added a commit
that referenced
this pull request
Jul 7, 2026
Ships on the SDK 1.5.3 / StartOS beta.9 line (the SDK 2.0 migration that requires beta.10 stays on `next`, PR #5, which will rebase onto this). - Bump upstream Hermes 2026.6.19 -> 2026.7.1 (the Judgment Release): Dockerfile FROM digest, HERMES_VERSION, release notes. Drop-in — no probe/schema/action changes needed (mirrors what next's bump touched). - Fix recurring Nous/OAuth token-refresh drops (#6): the provider and gateway health probes ran as root (image USER is root, runHealthScript takes no user), so their `import hermes_cli` created auth-store files (auth.lock/auth.json) root-owned and EACCES-locked the uid-1000 gateway out of refreshing its ~15-min access token. Run both probes as `hermes` (uid 1000), matching the daemons, so nothing on the volume is ever root-owned. Also refreshes the Dockerfile HERMES_UID/GID comment. Existing installs self-heal on the upgrade restart via the boot chown. Fixes #6 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
helix-nine
changed the title
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
Migrates this package to
@start9labs/start-sdk2.0, which requires StartOS 0.4.0-beta.10. This is nownext's only delta overmaster: the upstream Hermes2026.6.19 → 2026.7.1bump and the health-probe ownership fix already landed onmastervia #7 (released as2026.7.1:0on the SDK 1.5.3 / beta.9 line), andnextinherits both by rebasing onto it. Releases as2026.7.1:1— same upstream image, rebuilt on SDK 2.0 for beta.10.Changes
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 the other### Changed/### Removeditems from the SDK 2.0 changelog.startos/versions/current.ts→2026.7.1:1with SDK-2.0 release notes (all five locales). No state migration — packaging-only rework.Test plan
npm ci→tsc→ SDK lint →ncc→s9pk pack) for bothx86_64andaarch64.2026.7.1:0install to confirm the upgrade path is clean.ui) interface loads./opt/datastays hermes-owned (the release 2026.7.1:0: Hermes 2026.7.1 + health-probe ownership fix #7 fix, carried forward under SDK 2.0).