Repository navigation
ci(release): pin releases to the release PR commit - #2327
Merged
Merged
Conversation
Regenerating the release PR on every push to master closes it and discards the review edits it carries, which made most release PRs unmergeable. Prepare it on a daily schedule instead, and leave an open release PR untouched so it stays pinned to the commit it was prepared from. A manual run regenerates it, optionally from a given commit. Publishing still follows every push to master. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
Lines changed: production code 0, tests 0, other files ( 1 file changed, 41 insertions(+), 1 deletion(-), Untested properties:
Release PRs closed unmerged since 2026-10-01: #2067, #2214, #2215, #2240, #2254, #2255, #2260, #2281 and #2306. 🤖 Generated by Claude Code |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Benoît Cortier (CBenoit)
temporarily deployed
to
llm-providers
October 30, 2026 16:14 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Benoît Cortier (CBenoit)
changed the title
Member
Author
|
Updated: the daily run now always regenerates the release PR, and publishing runs only for a merged release PR, from its head commit ( Lines changed: production code 0, tests 0, other files ( 1 file changed, 49 insertions(+), 3 deletions(-), Untested properties:
🤖 Generated by Claude Code |
Benoît Cortier (CBenoit)
temporarily deployed
to
llm-providers
October 30, 2026 16:17 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
github-actions
Bot
added
breaking-change
This branch was previously deployed
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.
Regenerating the release PR on every push to master closes it and discards the review edits it carries, and publishing from master after the merge ships changes the release notes do not describe.
Regenerate the release PR once a day from the head of master, or on a manual run, optionally from a given commit. Publish only when a release PR is merged, and publish from that PR's head commit, so the published crates match the versions and changelogs it was reviewed with. Changes merged to master after its base commit go to the next release PR.
🤖 Generated with Claude Code