Repository navigation
chore: move to start-sdk 3.0.3; 1.102.4:1 → 1.102.5:0 - #17
Merged
Merged
Conversation
- pin @start9labs/start-sdk 3.0.3 and regenerate the lock against the live registry - drop the toolchain devDependencies and scripts the SDK supplies; .prettierrc names the SDK config - file models use z.looseObject; drop the redundant .passthrough() calls - exec timeouts move into the options object - empty sdk.Dependencies.of() builder, passed to buildManifest and setupInit - Stop Tailscale Serve warns before it runs - Serve Mode's description lists each offered mode on its own line - sync workflows (ready_for_review, pr-retarget.yml) and AGENTS.md to the template - ships under 1.102.5:0 (not yet on community-prod): its upstream notes, with this change's bullets under them Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
helix-a
approved these changes
Oct 8, 2026
helix-a
left a comment
Member
There was a problem hiding this comment.
Reviewed the diff at 4c70c1c: SDK 3.0.3 dependency/init wiring, exec timeouts, loose file-model schemas, action confirmation/descriptions, translations and workflow changes. No blocking findings. The SDK pin matches the latest npm release, and git merge-tree confirms a clean merge with origin/master.
Reused successful Build CI run 37715969546: discovery and both x86/arm package builds passed. No duplicate local build or runtime testing performed.
Helix-Harness: pi
Helix-Model: openai-codex/gpt-6.1-sol
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
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.
The SDK 3.0.3 migration for Tailscale, shipping with Tailscale 1.102.5. Builds on the file-model work in #11 by @marcwparrish.
npm audit0). The toolchain the SDK now supplies is dropped, and.prettierrcnames the SDK's shared config.z.looseObject.serve-routes.jsonandts-status.jsonkeep keys the package doesn't model; the two.passthrough()calls this made redundant are gone.exectimeouts move into the options object at both call sites (tailscale statusandtailscale serve status); the positional form no longer type-checks.sdk.Dependencies.of()builder, passed tobuildManifestandsetupInit, replacingsetupDependenciesand the manifest'sdependencies: {}.ready_for_review,pr-retarget.yml);AGENTS.mdresynced and its repo section cut to the four rules README doesn't carry; README and instructions updated.tailscaledrunning when it falls behind on status updates. The release notes give that, with this change's bullets under them.🤖 Generated with Claude Code