Support wheel dispatch from existing release tags - #24716
Merged
Conversation
Contributor
|
Contributor
Validation ReportAll 21 validations passed. Show details
|
AAraKKe
approved these changes
Jul 29, 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.
Summary
create-tagsinput to the shared wheel release workflow, defaulting totrueWhy
Legacy GitLab must remain the sole release-tag creator for integrations-extras and marketplace. Those repositories will dispatch this reusable workflow only after signing and pushing tags at the exact source SHA.
Verification
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python -m pytest tests/ -q— 134 passedpython -m compileall -q .git diff --checkorigin/master; no new workflow findingRollout
Merge this PR before enabling either source-repository handoff. Existing callers are unchanged because
create-tagsdefaults totrue.Coordinated PRs: