Repository navigation
Conversation
GITHUB_TOKEN can no longer create pull requests in the org; mint a token from the sdk-bot environment instead of re-enabling that setting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ae49519. Configure here.
| permission-pull-requests: write | ||
| - uses: googleapis/release-please-action@5c625bfb5d1ff62eadeeb3772007f7f66fdcf071 # v4.4.1 | ||
| with: | ||
| token: ${{ steps.app.outputs.token || github.token }} |
There was a problem hiding this comment.
Release PR CI skip never fires
Medium Severity
Release PRs now come from getstream-sdk-bot[bot], but release-only in ci.yml still matches only github-actions[bot]. That job never runs, so the unit lane no longer skips and 🧪 Tests waits on the full suite for every version bump.
Reviewed by Cursor Bugbot for commit ae49519. Configure here.
|
Hold until getstream-sdk-bot is installed on this repo, and on GetStream/chat and GetStream/protocol. It is not installed yet: today's regen runs fail with a 404 on the App installation lookup. Merging before that just moves the failure to the release job. |


Why
The 2026-11-20 org hardening turned off "Allow GitHub Actions to create and approve pull requests", so release-please can no longer open Release PRs with
GITHUB_TOKEN(e.g. stream-sdk-java run 44715449332). We're keeping that org setting off: it would also letGITHUB_TOKENapprove PRs, which bypasses review.What
The
release-prjob now opens the Release PR as getstream-sdk-bot, the same wayregen.ymlalready does:sdk-botenvironment (key stays branch-restricted there), scoped tocontents+pull-requestswrite onlyGITHUB_TOKENin this job drops tocontents: read(was contents/issues/pull-requests write)GITHUB_TOKENonesHotfix branches (
N.x) aren't allowed by thesdk-botenvironment, so there the job runs without the key on a read-only token. A push with nothing to release stays green. One with changes fails until the environment allows that branch. That path is already broken by the org setting, so this isn't a regression.Depends on
getstream-sdk-bot being reinstalled on this repo (it was uninstalled in the same cleanup).
Verify after merge
gh workflow run release.yml(or the next push to the default branch) → Release PR opened/updated bygetstream-sdk-bot[bot].🤖 Generated with Claude Code
Note
Medium Risk
Changes release automation authentication and hotfix Release PR behavior; default-branch releases depend on the sdk-bot app and environment being configured correctly.
Overview
Release PR creation no longer relies on
GITHUB_TOKENwrite access (blocked by org policy). Therelease-prjob now uses thesdk-botenvironment on the default branch to mint a short-lived getstream-sdk-bot token withcontentsandpull-requestswrite, and passes that token torelease-please. Job permissions are reduced tocontents: read.On hotfix branches (
N.x), the environment is omitted, so the job runs with a read-only token; runs with nothing to release stay green, but opening/updating a Release PR when there are changes will fail untilsdk-botcan run on that branch.Reviewed by Cursor Bugbot for commit ae49519. Bugbot is set up for automated code reviews on this repo. Configure here.