keep stable release pr open#52
Merged
Merged
Conversation
e864489 to
234199f
Compare
234199f to
087426b
Compare
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.
What Changed
release/stableand create/update the stable release PR, even when release package versions already match..github/release-pr/stable.jsonon the release branch so the PR has a real release marker diff.Why
After release infra fixes landed, package metadata still matched
2026.6.3000+tarik02, so the Release PR workflow reported unchanged metadata and skipped creating the follow-up release PR. We still need a persistent pending stable release PR until that release is merged.UI Changes
n/a
Checklist