Repository navigation
ci: mark pre-release tags as GitHub pre-releases - #2
Open
ale-rinaldi wants to merge 1 commit into
Open
ale-rinaldi wants to merge 1 commit into
ale-rinaldi wants to merge 1 commit into
Conversation
Tags like v1.2.0b1 / v1.2.0rc1 now produce a GitHub pre-release (PyPI already treats the version as a pre-release), so beta cuts are labelled consistently for the upcoming port-8888 test rounds. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This branch has not been 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
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.
Adds
prerelease:to the release job so PEP 440 pre-release tags(
v1.2.0b1,v1.2.0rc1) create a GitHub pre-release. Groundwork for theport-8888 support work, which we'll ship as betas.
No release is cut by this PR.
🤖 Generated with Claude Code