Conversation
The tagged commit is the Release PR's merge commit. Merges are squashed onto an up-to-date branch and release-please refreshes its PR on every push, so that commit's tree is the Release PR's tree: the version bump and changelog on top of an already-tested default branch. The Release PR already skips the lane, so running it after merge re-tested the same tree at the one point where a failure could no longer be fixed on the PR and instead left the release stuck on autorelease: pending. Release now matches chat's: merge, tag, publish.
mogita
commented
Sep 23, 2026
…tfixes - The Release PR skip now also requires every changed file to be one release-please writes. A release-only job lists the PR's files; a code change pushed onto a Release PR by hand, an unexpected file or a failed lookup runs the unit lane instead. Checked against the open Release PRs, which all still skip. - Releases from an N.x branch run the unit lane before tagging again. Hotfix commits are pushed there without a PR, so nothing else tested them. Releases from the default branch still tag directly. - The detect stand-down comment no longer refers to a test run, and the java and net docs no longer say publish_tag can fix a build that does not compile.
release accepted a skipped tests job under !cancelled(), so a detect job that wrote ready=true and then failed a later step still reached the tag. In getstream-go that later step is the go.mod major check, so an uninstallable major would have been tagged permanently. release now also requires needs.detect.result == 'success'.
… its version The allowlist let a whole file through, and pyproject.toml, uv.lock, composer.json, the csproj and Client.cs also hold dependencies or client code, so a hand-pushed dependency bump still skipped the lane. Now every added line in a version file must carry the new version from the manifest, and with versions masked the removed lines must match the added ones one for one. The file list reaches the inline script through a temp file, since a heredoc on python3 takes over its stdin. Checked end to end with the step as written: the open Release PRs in stream-py, getstream-php, getstream-net and getstream-go skip; ordinary PRs, an added dependency line, a dropped dependency line, an injected line and an extra file all run the lane.
This branch has not been 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
1 participant
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.
Ticket
CHA-5511
Problem
The Release PR skips the unit lane, but merging it ran the same lane on the merge commit before tagging. That commit has the Release PR's tree, so the run re-tested already-tested code at the one point where a failure leaves the release stuck on
autorelease: pending.Solution
Remove the pre-tag unit run.
releasenow needs onlydetect, so merging a Release PR tags and publishes directly, the same way chat releases. The docs and workflow comments that described the pre-tag gate are updated.How to verify
actionlint .github/workflows/release.yml .github/workflows/ci.yml