ci: scope release workflows to version tags#7341
Closed
Xuanwo wants to merge 3 commits into
Closed
Conversation
tisonkun
approved these changes
Mar 31, 2026
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.
Which issue does this PR close?
N/A.
Rationale for this change
Several release workflows still triggered on every git tag. After adding binding-specific tags like
dotnet-v..., that allowed unrelated release workflows to run for the wrong package.What changes are included in this PR?
This narrows the Rust, Python, and Dart release workflows to
v*tags so they only react to OpenDAL release tags and no longer get triggered by unrelated binding-specific tags.Are there any user-facing changes?
No user-facing changes. This only reduces unintended release workflow executions.
AI Usage Statement
Built with Codex using GPT-5.4 subagents.