release action permissions

[gilesknap]

Summary by CodeRabbit

• Chores
  • Updated the release workflow to include explicit permissions for tag-based releases.
  • This enables automated release runs to write release-related content and access package artifacts with the required scopes.

[coderabbitai]

Warning

Review limit reached

@gilesknap, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 83e69098-c631-425a-8dfa-eb002bffe61d

📥 Commits

Reviewing files that changed from the base of the PR and between 4ccf891 and 110471c.

📒 Files selected for processing (1)

• template/{% if git_platform == 'github.com' %}.github{% endif %}/workflows/build.yml.jinja

📝 Walkthrough

Walkthrough

The build workflow template’s release job now includes an explicit permissions block granting contents: write and packages: read.

Changes

Workflow Permissions

Layer / File(s)	Summary
Add release job permissions template/{% if git_platform == 'github.com' %}.github{% endif %}/workflows/build.yml.jinja	Adds a permissions block to the release job with contents: write and packages: read.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the main change: adding permissions for the release job in the workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch permissions

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@template/`{% if  git_platform == 'github.com' %}.github{% endif
%}/workflows/build.yml.jinja:
- Around line 124-125: The release job’s job-level permissions block is
overriding unspecified scopes to none, so update the permissions in the release
workflow section to explicitly keep packages: read alongside contents: write.
Use the release job block in the build workflow template to ensure the GHCR
image can still be pulled when the job starts from that container image.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ac73c080-41fe-42fa-8925-6d7875101cd5

📥 Commits

Reviewing files that changed from the base of the PR and between 5c97cc3 and 67cfeca.

📒 Files selected for processing (1)

• template/{% if git_platform == 'github.com' %}.github{% endif %}/workflows/build.yml.jinja