Require shared CI checks and make releases recoverable - #68
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.
A GitHub release failure currently forces the PyPI upload step to run again on retry, even when the package was already published. PRs and releases also have separate copies of the test matrix, and main has no required CI check.
This change moves lint and the nine test combinations into one reusable workflow, called by both PR CI and publishing. A stable
CIcheck fails if the shared checks fail, are skipped, or are cancelled. Main will require that check from GitHub Actions with an up-to-date branch, including for admins.PyPI upload and GitHub release creation now run in separate jobs. Re-running failed jobs can finish a release without repeating a successful upload. Existing published notes are preserved, drafts can be finished, and concurrent publication attempts for the same tag are serialized. The release guide documents the process and recovery command.
Validation: Actionlint passed. Local execution of the workflow shell steps covered all CI gate outcomes, matching and mismatched version tags, a branch dispatch, and new, existing, draft, and failed GitHub release creation. No application code or package version changed.