chore: skip release artifacts for pre-release tags#42
Merged
Conversation
Add if condition to build-cli and test jobs so that pre-release tags (e.g. v2.6.0-rc.1) do not trigger CLI binary builds or GitHub Release creation. This enables using semver pre-release tags for Go module resolution during cross-repo development.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the release workflow to avoid producing CLI binaries and GitHub Releases for semver pre-release tags (e.g., v2.6.0-rc.1), while still allowing those tags to be used as valid Go module versions across repos.
Changes:
- Add a job-level
if: "!contains(github.ref, '-')"guard tobuild-cli. - Add the same guard to
testto skip running tests on pre-release tag pushes.
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.
Adds
if: "!contains(github.ref, '-')"to bothbuild-cliandtestjobs in the release workflow.Why: Pre-release tags like
v2.6.0-rc.1should be valid Go module versions for cross-repo development, but should NOT trigger CLI binary builds or GitHub Release creation.How it works: Semver pre-release versions always contain a hyphen (
-). The condition skips the jobs when the tag ref contains one.Use case: During RFC-005 implementation,
capiscio-serverneeds to referencepkg/pip/from capiscio-core main. A pre-release tag gives us a clean semver reference without producing release artifacts.