Repository navigation
ci(release): promote plugins to stable on release tag push - #6461
Merged
Merged
Conversation
A plugins-YYYYMMNN tag push is stable: version from the tag, release type from its message, skipped when the workflow push paths did not change. The stable branch pull request lookup moves here from the workflows.
Promoting workflows also trigger on plugins-* tags and take the release type from get-environment; release-tag is skipped on tag pushes.
kduret
previously approved these changes
Oct 5, 2026
A failed git diff now fails the step instead of skipping promotion; the diff lists both sides of renames and leaves non-ascii paths unquoted.
pkriko
approved these changes
Oct 5, 2026
Tpo76
approved these changes
Oct 5, 2026
kduret
approved these changes
Oct 5, 2026
tuntoja
changed the title
Nivoky
added a commit
that referenced
this pull request
Oct 6, 2026
Resolve conflicts with #6461, which removed the "Get release type" step from the deliver jobs and moved release type detection to get-environment.yml. Keep develop's removal of that step, and bump the relocated actions/github-script call in get-environment.yml to v9.0.0 to match the rest of this update. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
4 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.
Fixes MON-202120 (follow-up of #6460)
Description
plugins-YYYYMMNNtag, whichrelease-newcreates, now promotes testing to stable. Themasterflow keeps working unchanged until cutover.get-environmentgains a new script,.github/scripts/release/get-release-tag-context.sh. For a release tag it:stable;release/hotfix);on.push.pathschanged since the previousplugins-*tag, which keeps "only changed modules promote".masterpushes, previously copied 12 times plus once inpackage-delivery, now lives only inget-environment, unchanged. It runs onpushevents only.tags: ["plugins-*"], and their promote steps useneeds.get-environment.outputs.release_type.release-tagis skipped on tag pushes.How this pull request can be tested ?
core/github/context, 15 scenarios: release and hotfix tags, and the unchanged master push, PR, testing and unstable paths.release-newrun, planned as the last step of MON-202120.