| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…action to v5 The release-please workflow fails with startup_failure because the caller job invoking publish.yml does not declare explicit permissions. Also migrates from archived google-github-actions to googleapis/release-please-action v5. Co-Authored-By: rlamb@launchdarkly.com <4955475+kinyoklion@users.noreply.github.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Fixes Release Please startup_failure by adding explicit permissions to the call-workflow-publish caller job. Also migrates from archived google-github-actions/release-please-action to googleapis/release-please-action v5.
Review & Testing Checklist for Human
Notes
Same fix pattern as dotnet-core PR #241. The google-github-actions/release-please-action repo is archived; googleapis/release-please-action is the active successor.
Link to Devin session: https://app.devin.ai/sessions/54e32482848742c19ebf9c374efdc833
Requested by: @kinyoklion
Note
Low Risk
Low risk CI-only change; it updates the Release Please GitHub Action and adds explicit job permissions for the reusable publish workflow, which could affect release automation if misconfigured.
Overview
Updates the Release Please workflow to use the maintained googleapis/release-please-action at v5.
Adds explicit id-token and contents permissions to the call-workflow-publish reusable-workflow caller job to avoid permission-related startup failures when publishing after a release is created.
Reviewed by Cursor Bugbot for commit 22887ce. Bugbot is set up for automated code reviews on this repo. Configure here.