Skip to content

keep stable release pr open#52

Merged
tarik02 merged 1 commit into
mainfrom
fix/release-pr-always-open
Jun 30, 2026
Merged

keep stable release pr open#52
tarik02 merged 1 commit into
mainfrom
fix/release-pr-always-open

Conversation

@tarik02

@tarik02 tarik02 commented Jun 30, 2026

Copy link
Copy Markdown
Owner

What Changed

  • Always push release/stable and create/update the stable release PR, even when release package versions already match.
  • Generate .github/release-pr/stable.json on the release branch so the PR has a real release marker diff.
  • Replace the generated release PR body with stable-release context and commits since the previous stable tag.
  • Let the release workflow recognize stable release PR merges through the release marker.

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

  • This PR is small and focused
  • I explained what changed and why
  • I included before/after screenshots for any UI changes
  • I included a video for animation/interaction changes

@github-actions github-actions Bot added size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. labels Jun 30, 2026
@tarik02 tarik02 force-pushed the fix/release-pr-always-open branch from e864489 to 234199f Compare June 30, 2026 21:53
@tarik02 tarik02 force-pushed the fix/release-pr-always-open branch from 234199f to 087426b Compare June 30, 2026 22:00
@tarik02 tarik02 merged commit 7c6b884 into main Jun 30, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant