Skip to content

ci(release): build a release candidate only when its tag was checked - #37

Merged
kristoflemmens merged 1 commit into
mainfrom
ci/release-candidate-check
Nov 17, 2026
Merged

kristoflemmens merged 1 commit into
mainfrom
ci/release-candidate-check

Conversation

@kristoflemmens

Copy link
Copy Markdown
Contributor

A release candidate's tag was built and published (PyPI, binaries, images) on any v*-rc.* tag. The shared release-please.yml now checks every rc tag (klconsultancy/workflows#19): its version must be the open release pull request's, and the tagged commit on its base branch. The release job's if: uses its new output release_candidate instead of github.ref_type == 'tag', so a wrong tag fails the check and builds and publishes nothing.

The pin moves to 5488c03 (klconsultancy/workflows main). This path only runs on a tag push, so it is first exercised by the next release candidate; a push to main is unchanged.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kristoflemmens
kristoflemmens merged commit 8a644a3 into main Nov 17, 2026
12 checks passed
@kristoflemmens
kristoflemmens deleted the ci/release-candidate-check branch November 17, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant