Skip to content

fix(weekly-release): grant id-token permission and require RELEASE_BOT_TOKEN#18257

Merged
pettinarip merged 2 commits into
devfrom
fix/weekly-release-permissions
May 22, 2026
Merged

fix(weekly-release): grant id-token permission and require RELEASE_BOT_TOKEN#18257
pettinarip merged 2 commits into
devfrom
fix/weekly-release-permissions

Conversation

@pettinarip
Copy link
Copy Markdown
Member

Summary

Two fixes to weekly-release.yml after the first manual test run on dev (run 26290559253) failed:

  • Grant id-token: write at the workflow level. anthropics/claude-code-action@v1 authenticates with Anthropic via GitHub OIDC and the failed run logged Could not fetch an OIDC token. Did you remember to add 'id-token: write' to your workflow permissions?
  • Drop the secrets.GITHUB_TOKEN fallback for RELEASE_BOT_TOKEN. The fallback looked safe but silently degraded: with GITHUB_TOKEN authoring the deploy PR, no pull_request workflows would fire on it (CI, Netlify preview), while Discord still reported success. Better to fail loudly if the bot token isn't set.

Test plan

  • Confirm RELEASE_BOT_TOKEN is set in repo secrets (currently a PAT scoped to ethereum/ethereum-org-website with Contents, PRs, Workflows R/W).
  • Re-trigger weekly-release.yml via workflow_dispatch and confirm the Run /prepare-release step no longer fails on OIDC.
  • Confirm the deploy PR (if one is opened) shows the bot identity as author and triggers downstream CI + Netlify preview.
  • If RELEASE_BOT_TOKEN is unset, confirm the workflow fails fast at the checkout / gh step instead of silently degrading.

The action authenticates with Anthropic via GitHub OIDC and fails with
"Could not fetch an OIDC token" without this permission. First test run
on dev (workflow run 26290559253) failed for this reason.
Falling back to GITHUB_TOKEN looks safe but silently degrades: the deploy
PR is created, but no pull_request workflows fire on it (CI, deploy
preview), and the Discord notification still reports success. Fail fast
instead if RELEASE_BOT_TOKEN is missing.
@pettinarip pettinarip requested a review from wackerow as a code owner May 22, 2026 13:37
@netlify
Copy link
Copy Markdown

netlify Bot commented May 22, 2026

Deploy Preview for ethereumorg ready!

Name Link
🔨 Latest commit 78e5aca
🔍 Latest deploy log https://app.netlify.com/projects/ethereumorg/deploys/6a105c351e04de00097b1392
😎 Deploy Preview https://deploy-preview-18257.ethereum.it
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
7 paths audited
Performance: 70 (🟢 up 6 from production)
Accessibility: 96 (no change from production)
Best Practices: 100 (🟢 up 1 from production)
SEO: 98 (🔴 down 1 from production)
PWA: 59 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added the tooling 🔧 Changes related to tooling of the project label May 22, 2026
Copy link
Copy Markdown
Member

@wackerow wackerow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good @pettinarip, sorry for the premature merge on #18220 but I think this should do it

GH_TOKEN: ${{ secrets.RELEASE_BOT_TOKEN || secrets.GITHUB_TOKEN }}
# Required: deploy PR must be authored by a bot token so downstream
# pull_request workflows fire.
GH_TOKEN: ${{ secrets.RELEASE_BOT_TOKEN }}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, I see this loaded now, thanks

permissions:
contents: write
pull-requests: write
id-token: write
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@pettinarip pettinarip merged commit 66bd29c into dev May 22, 2026
21 of 22 checks passed
@pettinarip pettinarip deleted the fix/weekly-release-permissions branch May 22, 2026 13:57
@claude claude Bot mentioned this pull request May 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tooling 🔧 Changes related to tooling of the project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants