fix: upgrade release-please-action v3 → v4 (Node 24 compatibility) - #1322
Merged
Conversation
The deprecated release-please-action@v3 is now force-run on Node 24 (GitHub's Node 20 EOL took effect 2026-06-02), which breaks its bundled octokit and surfaces as a misleading "Resource not accessible by integration" error when creating the GitHub release. The token has contents:write — the failure is the action, not permissions. The last successful release (8.19.3, 2026-04-24) ran the same action SHA on Node 20. v4 is Node 24-compatible and keeps the same simple inputs (release-type/package-name/command), matching appfolio/browser-reporter. Bump both release-please.yml and release-please-pr.yml.
mdalpozzo
approved these changes
Jun 17, 2026
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
2 participants
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.
Summary
Upgrades
release-please-actionfrom@v3to@v4in both release workflows to fix the failingrelease-pleasejob on master.Root cause
The
release-pleasejob has been failing at release creation with:This is not a token-permissions issue — the runtime log confirms the
GITHUB_TOKENis grantedContents: write(and write on issues/pull-requests/etc.). The actual cause is the Node runtime:release-please-action@v3(SHAdb8f2c60)Contents: writeContents: writeGitHub's Node 20 EOL took effect 2026-06-02, force-running the deprecated v3 action on Node 24. v3's bundled octokit/fetch stack breaks on Node 24 and surfaces as a misleading
Resource not accessible by integration. The last good release ran the same action SHA on Node 20.Fix
Bump to
@v4(Node 24-compatible) in bothrelease-please.ymlandrelease-please-pr.yml. v4 keeps the same simple inputs (release-type/package-name/command), matching the workingappfolio/browser-reportersetup — so this is a one-line-per-file change with no config migration.Impact
Once merged, the
release-pleasejob should successfully tag v8.19.4 off the already-merged release PR #1318, flip itsautorelease: pendinglabel totagged, and unblock the release cycle (which is currently wedged — no new release PRs open while #1318 is untagged).Notes