Skip to content
This repository was archived by the owner on Nov 10, 2026. It is now read-only.

ci: create releases with the built-in token instead of the release app - #401

Merged
deanq merged 2 commits into
mainfrom
ci/release-token-drop-issues
Oct 30, 2026
Merged

deanq merged 2 commits into
mainfrom
ci/release-token-drop-issues

Conversation

@justinwlin

@justinwlin justinwlin commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

The Release job fails at token creation: The permissions requested are not granted to this installation (422). Since #399, the token step asks the release app runpod-release-please for contents, issues, pull-requests and workflows. The app only has contents: write, pull_requests: write and metadata: read (gh api apps/runpod-release-please-bot). Granting more needs an org owner.

This drops the app token and gives release-please the built-in GITHUB_TOKEN, as runpod-python does. The workflow already grants contents, pull-requests and issues write.

Why this works for 1.21.1

  • Release PR chore: release 1.21.1 #391 is merged, so release-please only has to create the release and tag.
  • github-actions[bot] created runpod-python v1.9.0 to v1.12.0 with the built-in token, and those release ranges changed .github/workflows/. So the token can tag releases like this one.
  • PyPI publish runs in the same workflow run from release_created, and no flash workflow triggers on release events. The built-in token not triggering other workflows doesn't matter here.

Trade-off
#97 moved to the app because the built-in token stopped working, most likely because flash disallows Actions from creating PRs. If that setting is still off, release-please can't open the next release PR with this token. runpod-flash stopped getting fixes on 2026-10-29, so 1.21.1 is expected to be the last release.

After merge
The push to main runs Release. It should create v1.21.1 and publish to PyPI from the GitHub-hosted runner (#400). Merge runpod-workers/flash#112 first (worker 1.6.1), because 1.21.1 includes #390.

Loading
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants