ci: Fix release workflow running too often #1500
Merged
+1
−1
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
on.create triggers on any tag *or branch* creation, and doesn't have a filter `on.push.tags`. (https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#create) The correct way to only run a job when a tag matching a pattern is pushed is via `on.push.tags`. (https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-of-specific-tags-occurs)
sc68cal
approved these changes
Dec 16, 2025
Contributor
|
I'd have to look at this further, since shouldn't the |
sc68cal
approved these changes
Dec 16, 2025
Contributor
|
Let's give it a try at least. I'll see if there's another PR we can merge and see if this stops triggering the release |
Contributor
|
Maybe the regex needs to be changed to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Related Issue
#1465
#1489
New Behavior
Don't run the release action of the CI pipeline for every new branch. Instead, only run it for tags that start with "v"
Contrast to Current Behavior
The action runs on every branch creation, as visible here
Discussion: Benefits and Drawbacks
Changes to the Documentation
n/a
Proposed Release Note Entry
n/a
Double Check
develbranch.