Skip to content

fix(release): fail loud when a release PR should exist but doesn't#68

Merged
ankitTelnyx merged 1 commit into
mainfrom
fix/release-pr-assert
Jul 9, 2026
Merged

fix(release): fail loud when a release PR should exist but doesn't#68
ankitTelnyx merged 1 commit into
mainfrom
fix/release-pr-assert

Conversation

@ankitTelnyx

Copy link
Copy Markdown
Collaborator

Follow-up to the --local scan fix: converts any future "no release PR" regression from a silent green run into a red one.

Logic: after the release-pr + sync steps (next pushes only), count feat:/fix:/Release-As commits in latest_tag..HEAD; if any exist and no open release-please--* PR is found (3 attempts, 10s apart), fail with ::error. Skips cleanly when there are no releases yet, the tag isn't in the clone, or there's genuinely nothing user-facing.

🤖 Generated with Claude Code

The release-pr CLI call is wrapped in `|| true`, so an API error or a
scan regression leaves the run green with no release PR — exactly how
the 2026-07-09 silent skip hid for weeks. This assertion fails the run
loudly when next carries user-facing (feat/fix) or Release-As commits
since the latest release but no open release-please PR exists.
@ankitTelnyx ankitTelnyx merged commit a11fc73 into main Jul 9, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant