Repository navigation
chore: drop the release version line gate - #62
Merged
Merged
Conversation
Remove RELEASE_VERSION_LINE and the two line-gate rejections from the release policy. Releases are manual workflow dispatches on the default branch where the version is typed deliberately, the registry is internal with an unpublish corrective, and the gate only imposed a recurring multi-file edit on every version line transition. Channel inference, exact SemVer validation, dispatch gating, registry pinning, and the integrity and source-SHA bindings are unchanged.
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
RELEASE_VERSION_LINEand the two version-line rejections fromscripts/release/policy.mjs. Any exact SemVer version can now be dispatched directly; the channel is still inferred from its shape (X.Y.Z→ stable/latest,-insiders.→ insiders,-alpha.→ alpha,-dev.→ dev).0.5.xline.Why
The gate bought no protection in our operating model: releases are manual workflow dispatches on the default branch (the typed version is the deliberate act), the registry is internal with an unpublish corrective, and the gate's only effect was forcing a recurring multi-file edit (manifests of test fixtures included) on every version line transition — demonstrated live by #60 and reverted by #61. Per the standing bar: no defensive measures without a concrete accident class they prevent and no recurring maintenance cost.
Unchanged
Channel inference, exact SemVer validation, dispatch-only context gating, registry pinning, manifest structure checks, publisher integrity and source-SHA bindings, and all tests (fixtures degrade to plain valid SemVer strings; 12/12 release tests pass, no test edits needed).
Notes
Published releases (including 0.6.0) are unaffected; no re-release is needed or performed.