Repository navigation
fix(release): prepare release candidates explicitly - #61
Merged
Merged
Conversation
choskeli
force-pushed
the
fix/freeze-release-candidate
branch
from
October 28, 2026 04:21
2b7a173 to
54ca836
Compare
choskeli
marked this pull request as ready for review
October 28, 2026 04:30
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.
Main pushes currently rewrite Release Please candidates and invalidate their checks. Prepare/refresh proposals only on explicit Release Please dispatch; pushes still process merged release PRs into their exact tags and drafts.
Based on merged #60,
68cb2607613b9498150db4380cafa4f31d57a227. The rebase preserved the tested tree exactly and does not restore #55's queue code.skip-github-pull-requestinput. No custom release state machine, publisher change, parser change, credentials change, or live settings change.pull_request_target; CI approval alone does not trigger its title result. After explicit preparation, a maintainer reopens the PR and verifies both current-head required checks.Validation:
npm run checkis not green: sandbox loopback was blocked; a permitted native Windows coverage rerun passed 2,125 tests and failed 6 socket-close cases. Those same 6 failures reproduce on unchanged revert: remove native merge queue integration #60 base. The existing publisher fixture suite uses POSIX fake-gh lookup and does not execute correctly on native Windows. Hosted Linux checks remain required.Head:
2b7a1733e5f48c40302c9273d6434684db71d1b4. Draft pending hosted checks. No release was dispatched or published.