feat: make ship workflow versionless - #2702
Closed
carl-eriksen wants to merge 1 commit into
Closed
Conversation
Remove automatic release metadata from ordinary shipping while retaining explicit release utilities and documentation paths.
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
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.
Summary
/shipruns./document-releasemode that never changes release metadata.gstack-version-bump,gstack-next-version, version-source helpers, collision checks, and version-title tooling for explicitly invoked release workflows.Test Coverage
The versionless shipping contract verifies that
/shipdoes not invoke version allocators, write VERSION/manifests/CHANGELOG, ask for a bump tier, emit release metadata, or create version-prefixed PR titles. Existing generator, required-read, title-helper, and host-output coverage remains in place.Pre-Landing Review
No issues found. Retained release utilities have documentation-only ownership changes; their release behavior remains covered by their existing tests.
Eval Results
No model prompt implementation changed; evals were not required.
Plan Completion
All requested versionless-shipping requirements are implemented. Explicit release/version utilities were intentionally retained.
Documentation
Source templates and generated Claude, Codex, Factory, OpenClaw, and skill-index documentation were regenerated and verified fresh.
Test plan
bun run test:free— 8,065 passed across 7 shardsbun run gen:skill-docs— generated documentation refreshedgit diff --check— passedNotes
bun run skill:checkstill exits 1 on the pre-existing trackedclaude/SKILL.md.tmplwithout a generatedclaude/SKILL.md; all generator freshness checks pass.