Fix 403 Forbidden on GHCR push by adding attestations permissions#58
Conversation
Added `attestations: write` and `id-token: write` to `docker.yml`. This is required for `docker/build-push-action` v6+ which generates provenance attestations by default. Without these permissions, the action fails to push the attestation to GHCR.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
…739309188844099428 (#59) Fix 403 Forbidden on GHCR push by adding attestations permissions
Updated
{{cookiecutter.project_slug}}/.github/workflows/docker.ymlto includeattestations: writeandid-token: writepermissions. This fixes the "403 Forbidden" error users encounter whendocker/build-push-actiontries to push provenance attestations to GHCR.PR created automatically by Jules for task 1739309188844099428 started by @gowthamrao