chore: migrate to start-sdk 2.0 and refresh Readstr to upstream b3081df#2
Open
helix-nine wants to merge 1 commit into
Open
chore: migrate to start-sdk 2.0 and refresh Readstr to upstream b3081df#2helix-nine wants to merge 1 commit into
helix-nine wants to merge 1 commit into
Conversation
helix-nine
changed the title
Rebases `next` onto `main` after PR #5 merged, and collapses the branch to the work that is actually still outstanding. PR #5 independently did the Readstr submodule refresh this branch was carrying (both landed on 985ab25) and released it as 0.1.0:1. So the submodule bump and its release notes are now redundant here — the notes in particular would have re-announced, under 0.1.0:2, the whole feature list (AI summaries, Nostr view sync, OPML, smart views, reading history) that 0.1.0:1 already shipped. Dropped both. The submodule is unchanged relative to main. What remains, and all this version actually contains, is the start-sdk 2.x migration: SDK 1.5.3 → 2.0.5, the accompanying source changes (main.ts, interfaces.ts), the build plumbing moving to the SDK-shipped s9pk.mk and tsconfig.base.json (dropping the vendored s9pk.mk), and the release notes reduced to "Internal updates (start-sdk 2.0.x)" to match. Also keeps this branch's CI fix rather than letting the rebase regress it: main's workflows point at `start9labs/shared-workflows`, which is retired — the callers here reference `Start9Labs/start-technologies` instead. Verified: lockfile resolves start-sdk 2.0.5 with no nested stale copy and is at a fixed point; `npm run check` (tsc --noEmit) green.
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 (requires StartOS 0.4.0-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 other### Changed/### Removeditems from the SDK 2.0 changelog.Upstream refresh (Readstr)
Readstr publishes no releases, so the upstream is pinned as the
readstr/git submodule trackingmain(perUPDATING.md). Advanced the submodule7299c5a→b3081df; upstream's nominal version stays0.1.0, so the StartOS revision remains0.1.0:1(a single release abovemain's0.1.0:0) and the release notes now cover both this refresh and the SDK 2.0 update.:8444port from the default extension web-app URL.No state migration is required (
migrations.upstays a no-op,downstaysIMPOSSIBLE).Test plan
npm ci→tsc→ SDK lint →ncc→s9pk pack)..s9pk(version0.1.0:1) on a StartOS 0.4.0-beta.10 server.readstr-subapp andpostgres-subdatabase subcontainers come up and the service reaches its health check anduiinterface.uiinterface via NIP-98 (Tor /.local/ LAN hostname) to confirmNIP98_ALLOWED_HOSTSis populated.Backups.withPgDumpfix); restore it into a fresh install and confirm data returns.0.1.0:0build, then upgrade to this build and confirm data and config are preserved.🤖 Generated with Claude Code