Repository navigation
fix(release): handle missing release PR output - #5
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully 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.
After release PR #4 was merged, Release Please correctly returned no new PR while awaiting the v0.2.0 tag. GitHub evaluated the CI dispatch step's environment expression and failed on fromJSON(''), despite the conditional guard.
Default the optional PR output to an empty JSON object before parsing it. The existing prs_created condition still prevents CI dispatch when no release PR was created or updated.
Validation: confirmed the failure in run 35458203270, parsed the updated workflow YAML, and passed all five release-note tests. This change only touches the workflow; document deletion remains excluded.