Skip to content

fix(ci): pin release-please-action to v4, releases are broken on v5 - #20

Merged
ExtraToast merged 2 commits into
mainfrom
fix/release-please-v4
Sep 2, 2026
Merged

fix(ci): pin release-please-action to v4, releases are broken on v5#20
ExtraToast merged 2 commits into
mainfrom
fix/release-please-v4

Conversation

@ExtraToast

Copy link
Copy Markdown
Contributor

release-please-action v5.0.0 computes the release correctly and then fails to create it:

✔ Creating 1 releases for pull #17
release-please failed: Resource not accessible by integration
  https://docs.github.com/rest/releases/releases#create-a-release

Reproduced on both client repos with contents: write on the job — the permission that endpoint documents. Reverting rather than debugging, because right now no release can be created at all.

Also worth recording: ordinary CI does not exercise release.yml, so this major went in on a green PR. The Actions ecosystem now ignores this action's majors until v5 is understood.

v5.0.0 reads the configuration and computes the release correctly, then fails
creating it:

  ✔ Creating 1 releases for pull #17
  release-please failed: Resource not accessible by integration

Reproduced on both client repositories with `contents: write` on the job,
which is the permission that endpoint documents. Reverted rather than debugged,
because the effect is that no release can be created at all.

Worth recording why this got in: ordinary CI does not exercise release.yml, so
a green pull request says nothing about whether releasing still works. The
Actions ecosystem now carries an ignore for this action's majors until v5 is
understood.
@ExtraToast
ExtraToast merged commit 5495f38 into main Sep 2, 2026
4 checks passed
@ExtraToast
ExtraToast deleted the fix/release-please-v4 branch September 2, 2026 21:33
@github-actions github-actions Bot mentioned this pull request Sep 2, 2026
github-actions Bot added a commit that referenced this pull request Sep 2, 2026
🤖 I have created a release *beep* *boop*
---


<details><summary>1.0.0</summary>

##
[1.0.0](v0.2.4...v1.0.0)
(2026-09-02)


### ⚠ BREAKING CHANGES

* **kotlin:** generate against Jackson 3 and Spring Boot 4
([#25](#25))

### Features

* generated Brevo clients with spec-derived versioning
([fb81701](fb81701))
* **kotlin:** generate against Jackson 3 and Spring Boot 4
([#25](#25))
([db41203](db41203))


### Bug Fixes

* **ci:** pin release-please-action to v4, releases are broken on v5
([#20](#20))
([5495f38](5495f38))
* **ci:** stop creating workflow runs that cannot execute, and verify
releases properly
([#18](#18))
([f28d49d](f28d49d))
* **ci:** take the release pull request number from release-please
([#14](#14))
([5902f9f](5902f9f))
* **deps:** raise axios, yaml and js-yaml above known advisories
([fc2537b](fc2537b))


### Documentation

* describe the unattended release chain and its one gap
([#12](#12))
([fdf4e58](fdf4e58))


### Build and Dependencies

* **deps-dev:** bump @types/node from 24.9.2 to 26.3.0 in /typescript
([#6](#6))
([6e0c7d8](6e0c7d8))
* **deps-dev:** bump typescript from 5.9.3 to 6.0.3 in /typescript
([#19](#19))
([e62663f](e62663f))
* **deps:** bump actions/checkout from 5.0.0 to 7.0.1
([#9](#9))
([fc41142](fc41142))
* **deps:** bump actions/dependency-review-action from 4.7.2 to 5.0.0
([#11](#11))
([ee9474a](ee9474a))
* **deps:** bump actions/setup-node from 6.0.0 to 7.0.0
([#10](#10))
([7a06984](7a06984))
* **deps:** bump actions/upload-artifact from 4.6.2 to 7.0.1
([#21](#21))
([859cd79](859cd79))
* **deps:** bump googleapis/release-please-action from 4.2.0 to 5.0.0
([#8](#8))
([ea8555b](ea8555b))
* **deps:** bump gradle/actions/setup-gradle from 4.4.1 to 6.3.0
([#22](#22))
([376e7d5](376e7d5))
* **deps:** bump the actions group with 4 updates
([#7](#7))
([3d6fefc](3d6fefc))
* **deps:** Bump the gradle group in /kotlin with 5 updates
([#2](#2))
([3a408dc](3a408dc))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant