Repository navigation
Enforce patch-only releases in CI and release commands - #29
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Versioning and publishing must keep durable-harness on 0.0.x. A generic request to ship a release must not authorize moving to 0.1.0 or 1.0.0.
Run the existing release-line guard in a dedicated CI job and before both
ci:versionandci:publish. Add 11 regression tests using the real Changesets planner: patch and consumed release PRs pass; minor/major changesets and manually edited versions outside 0.0.x fail, including prereleases. Document that changing the release line requires an explicit human maintainer decision and a separately reviewed policy change, and add that instruction to AGENTS.md.Validation:
pnpm check:changesets(11 tests plus the current release plan),node scripts/check-public.mjs, andgit diff --checkpass. A disposable-workspace smoke test runs the realpnpm ci:versioncommand and confirms a patch versions 0.0.1 to 0.0.2 without publishing. No published package code or version changes.