Repository navigation
Separate tag-triggered release builds from CI - #1
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
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.
Outcome
PR and branch CI now runs source quality checks and the existing CPU/offline contract suite without building distributions. A separate
Build releaseworkflow builds and audits sdist/wheel artifacts, verifies checksums, and exercises wheel installation when av*tag is pushed. The tag must exactly matchvplus the package version before building.The build and installation checks retain their existing commands and read-only repository permissions. Build and quality tools use isolated venvs. Contributor and release documentation describe the triggers, validation requirements, and Actions artifact handling; the workflow does not publish a GitHub Release or to PyPI.
Verification
bash -non all run blocks, local Markdown file-link checks, andgit diff --check.75ee7bdfe5dc5816e1161aaaa2efd7979cf88a66and selected onlyqualityandcpu-contract-tests. Both jobs failed before starting because GitHub reported failed account payments or an insufficient spending limit. No source checks or tests executed; rerun after the billing restriction is resolved. No release-build run was triggered by this PR.Compatibility and provenance
quality-and-packagetoquality.