ci(release): use get_prs_between_tags with fail_on_error

[mokagio]

AI-generated below:

What?

Bumps fastlane-plugin-wpmreleasetoolkit to 15.0.0 and switches generated_release_notes back to the get_prs_between_tags action, now passing fail_on_error: true.

Closes CMM-2332 / #591.

Why?

#588 deliberately bypassed the action and called GithubHelper#generate_release_notes directly, because the action rescued every StandardError and returned the message as the changelog — 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 has to fail the step instead.

release-toolkit#772 added the opt-out, and it has now shipped in 15.0.0, so the workaround can go.

How?

fail_on_error: true is load-bearing rather than cosmetic, which is the one thing the diff doesn't say on its own — hence the comment that replaces the old workaround note.

The major bump is manual: Dependabot only proposes this repo's toolkit updates through the ruby-minor-and-patch group. Neither of 15.0.0's breaking changes reaches this repo — there are no *_build_preflight call sites, and EnvManager now populating the process ENV by default is a no-op here, where no .env file ships.

Testing Instructions

The release lane only runs on CI, so I exercised the action directly against the live API from this branch:

bundle exec fastlane run get_prs_between_tags \
  repository:wordpress-mobile/GutenbergKit tag_name:v0.19.0 \
  previous_tag:v0.18.1 fail_on_error:true

Returns the v0.18.1 → v0.19.0 notes. Swapping in a nonexistent previous_tag exits 1 with Octokit::BadRequest: 400 - Invalid previous_tag parameter, where the same call with fail_on_error:false exits 0 and hands back the ❌ Error computing the list of PRs… string — i.e. exactly the failure this change exists to prevent.

Heads-up for whoever reads the next release page: the action rewrites GitHub's ## What's Changed heading into ## New PRs since [<previous_tag>](<link>).

[Copilot]

Pull request overview

Updates the CI release tooling to use the get_prs_between_tags Fastlane action again (now that it can fail the lane on API errors), preventing releases from being published with an error string as the GitHub Release body.

Changes:

• Bump fastlane-plugin-wpmreleasetoolkit from 14.11.3 to 15.0.0.
• Switch generated_release_notes from calling Fastlane::Helper::GithubHelper#generate_release_notes directly back to get_prs_between_tags.
• Pass fail_on_error: true (and keep token plumbing) so API failures stop the release step.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
Gemfile	Bumps the release-toolkit plugin constraint to ~> 15.0.
Gemfile.lock	Locks the plugin to 15.0.0 with updated checksum.
fastlane/Fastfile	Uses get_prs_between_tags(..., fail_on_error: true) for release notes generation to fail hard on API errors.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[wpmobilebot]

XCFramework Build

This PR's XCFramework is available for testing. Add the following to your Package.swift:

.package(url: "https://github.com/wordpress-mobile/GutenbergKit", branch: "pr-build/607")

_{Built from aea5c59}

[iangmaia]

👍 Thanks for addressing this.