fastlane/Fastfile builds the GitHub Release body by calling
Fastlane::Helper::GithubHelper#generate_release_notes directly, rather than the
get_prs_between_tags action that wraps it.
That was a deliberate workaround: the action rescued every StandardError and
returned the message as the changelog, so a transient API failure would publish a
release whose notes read ❌ Error computing the list of PRs…. We push the tag
before creating the Release, so that needs to fail the step instead.
wordpress-mobile/release-toolkit#772 added a fail_on_error: parameter and is
merged, but not yet in a released gem — we're pinned to ~> 14.11, locked at
14.11.3, and the entry is still under ## Trunk in the toolkit CHANGELOG.
Once it ships:
fail_on_error: true is required, not optional. Without it the action swallows the
400 Invalid previous_tag parameter that a malformed previous_tag produces and
publishes the error text as the release body — the exact failure #772 exists to
prevent.
Context: #588
fastlane/Fastfilebuilds the GitHub Release body by callingFastlane::Helper::GithubHelper#generate_release_notesdirectly, rather than theget_prs_between_tagsaction that wraps it.That was a deliberate workaround: the action rescued every
StandardErrorandreturned the message as the changelog, so a transient API failure would publish a
release whose notes read
❌ Error computing the list of PRs…. We push the tagbefore creating the Release, so that needs to fail the step instead.
wordpress-mobile/release-toolkit#772 added a
fail_on_error:parameter and ismerged, but not yet in a released gem — we're pinned to
~> 14.11, locked at14.11.3, and the entry is still under## Trunkin the toolkit CHANGELOG.Once it ships:
fastlane-plugin-wpmreleasetoolkitinGemfile.lockto a versioncontaining #772
generated_release_noteshelper'sGithubHelpercall withget_prs_between_tags(..., fail_on_error: true)fail_on_error: trueis required, not optional. Without it the action swallows the400 Invalid previous_tag parameterthat a malformedprevious_tagproduces andpublishes the error text as the release body — the exact failure #772 exists to
prevent.
Context: #588