Skip to content

Publish CLI nightlies and stable packages from accepted SDK releases on main - #71

Merged
purpshell merged 1 commit into
mainfrom
t3code/main-release-pipeline
Oct 4, 2026
Merged

purpshell merged 1 commit into
mainfrom
t3code/main-release-pipeline

Conversation

@purpshell

@purpshell purpshell commented Oct 4, 2026 •

Copy link
Copy Markdown
Member

Moves CLI development and package publication to one main branch. Nightlies skip unchanged CLI/SDK combinations and require an exact published SDK with matching staging API acceptance; stable packages require production acceptance and an explicit version.

The build pins the selected SDK in its manifest and lockfile, verifies the CLI, then packs and installs a clean consumer to check both runtime versions. Release artifacts preserve CLI, SDK and API source/spec/acceptance evidence; registry verification checks immutable tarball integrity. Feature-to-Linear stage receipts are emitted for a later posting bot. The private source repository preserves public npm provenance=false.

Validation: 1,027 CLI tests, 2 release gate tests, typecheck, lint, format, build, pack dry run and production audit pass. Publication workflow passes Actionlint. Main was created at the existing reviewed dev head 09fc034 without removing dev or altering another worktree.

API and SDK contract gate: updated through exact published SDK provenance. CLI: publication and branch routing updated. Docs: README and RELEASING.md updated. Feature releases: nightlies and stable availability remain separate from source merge; publication stays blocked until the SDK has matching accepted-release provenance. Admin, onboarding, billing/PAYG, Usage and Analytics are unaffected because this change adds no product authority, billable quantity or tracking. Linear ticket identifiers and stable publishing configuration remain operator dependencies.

Depends on SDK PR polymorfa/sdks#335.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.

@coderabbitai

coderabbitai Bot commented Oct 4, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)
  • dev

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Team
  • Run ID: 44823255-9328-4d26-abeb-41376c9e6d1d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@purpshell
purpshell merged commit 43e55a4 into main Oct 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant