ci(agent-helper): publish via GITHUB_TOKEN instead of GitHub App token - #777
Conversation
The GHCR publish authenticates via the GitHub App token, not GITHUB_TOKEN, so the packages:write job permission was unused. The org package now exists (bootstrapped by a first manual push), so App-token pushes succeed once the App is granted write access to the package. Bumps images/agent-helper/VERSION to 1.0.0.
The GitHub App cannot be granted write access to the org container package, so switch GHCR auth to the built-in GITHUB_TOKEN with packages:write. This is the standard method and lets the package be published under the repo. Drops the create-github-app-token step and restores packages:write.
✅ Deploy Preview for devsydev canceled.
|
|
Warning Review limit reached
Next review available in: 21 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ Deploy Preview for images-devsy-sh canceled.
|
1 participant
Summary
Switches the agent-helper GHCR publish from the GitHub App token to the built-in
GITHUB_TOKEN.The GitHub App (
devsy-app) has org-levelpackages: write, but org container packages use per-package access control and the App cannot be added to the package's access list. That left App-token pushes failing withinstallation not allowed to Write organization package.Using
GITHUB_TOKEN(withpackages: write, restored here) is the standard method and authorizes the push via the repo running the workflow.Changes
packages: writeto the job.create-github-app-tokenstep.github.actor/secrets.GITHUB_TOKEN.Follow-up (org admin)
For
GITHUB_TOKENto write the existing package, grant the repo access: package settings → Connect repositorydevsyand Manage Actions access →devsy= Write.