Repository navigation
release: classify 0.x versions as prereleases - #12
Merged
Merged
Conversation
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.
Requirement
Treat the user-selected
v0.1.0initial-development release as a GitHub prerelease while keeping its SemVer tag and package version unchanged.Behavior and trust boundary
The draft workflow now passes
--prereleaseforv0.x.yas well as tags with a SemVer prerelease suffix. The tag-signature, source-revision, validation, CodeQL, package-integrity, and draft-only gates are unchanged.v1.0.0remains a normal GitHub release. No token-validation or PostgreSQL behavior changes.Verification
actionlint -color=false .github/workflows/release.ymlv0.1.0,v0.1.0-rc.1,v1.0.0-rc.1, andv1.0.0./scripts/ci/check-source-tree.shgit diff --checkThe actual tag-triggered workflow remains untested until a signed tag is pushed. The earlier v0.1.0 candidate run passed on the pre-change main commit; final package evidence must be generated again from the tagged revision. Rollback is reverting this classification change before tagging. Publication still follows
docs/release-readiness.md.