ci: Sequence release publication and PR generation - #350
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Run release-pr generation after release-plz publishes and tags, so the fresh checkout calculates the next release against the new tag. Keep stale branch cleanup scoped to closed PRs for the release line and update release-train instructions.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #350 +/- ##
=======================================
Coverage 76.42% 76.42%
=======================================
Files 4 4
Lines 1073 1073
=======================================
Hits 820 820
Misses 253 253 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
scouten-adobe
commented
Sep 25, 2026
| echo "$RELEASES" | ||
| echo "===========================" | ||
|
|
||
| release-pr: |
Collaborator
Author
There was a problem hiding this comment.
This mirrors a recent changes made in contentauth/c2pa-rs#2698 and should fix the race condition that allowed for release PR misfires.
ok-nick
approved these changes
Sep 25, 2026
scouten-adobe
changed the title
scouten-adobe
added
the
backport-stable
scouten-adobe
enabled auto-merge (squash)
September 25, 2026 20:23
Collaborator
|
Backport-action failed to backport this pull request in workflow run 36186036296.
❌ stable — unable to cherry-pickTried to cherry-pick commits onto Please cherry-pick the changes locally and resolve any conflicts: git fetch origin stable
git worktree add -d .worktree/backport-350-to-stable origin/stable
cd .worktree/backport-350-to-stable
git switch --create backport-350-to-stable
git cherry-pick -x 3f0165c2f7af3fb859a780449c022481dac8b9f2 |
This was referenced Sep 25, 2026
Merged
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
3 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.
Summary
release.yml, after the publish job succeeds. A fresh checkout with full tag history then sees any tag created by publication before calculating the next release, avoiding stale release PRs like chore: release v0.29.0-dev #349.release-pr.yml, which could race with publishing on the same release-line push and could be manually dispatched onmain.release-plz-*PR branches for the current base line, preventing cleanup onstablefrom deleting another release line's active branch.The combined workflow remains triggered only on
stableandv0.*, so active and retired release lines use the same ordered release process.Validation
actionlintpassed for the updated release and promotion workflows.git diff --checkpassed.After review and merge to
main, this can be backported tostable.