fix(ci): update OIDC repo references and upgrade Node.js 20 actions#395
fix(ci): update OIDC repo references and upgrade Node.js 20 actions#395
Conversation
…ns/configure-aws-credentials@v6 across multiple workflows
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 Tip You can customize the high-level summary generated by CodeRabbit.Configure the |
Gateway deploy was failing with
Not authorized to perform sts:AssumeRoleWithWebIdentitybecause OIDC trust policies still referenced the oldeliza-cloud-v2repo name.Also upgrades GitHub Actions flagged for Node.js 20 deprecation (forced to Node.js 24 starting June 2, 2026).
Changes
OIDC fix — repo rename
eliza-cloud-v2→cloud:infra/terraform/tfvars/development.tfvars/production.tfvars—github_repoinfra/terraform/variables.tf— default valueinfra/charts/gateway-discord/values.yaml— image repository pathinfra/terraform/README.md,infra/charts/gateway-discord/README.md— trust policy examplesinfra/local/setup.sh,infra/local/smoke-test.sh— script referencesdocs/ONBOARDING_INTEGRATION_PLAN.mdNode.js 24 action upgrades:
actions/checkoutv4 → v5 (all workflows)aws-actions/configure-aws-credentialsv4 → v6 (gateway-discord)docker/build-push-actionv5 → v6 (gateway-discord)Manual step required
The
github-actions-gateway-terraformIAM role trust policy must be updated in AWS to referenceelizaOS/cloudbefore this workflow can run. See terraform README for the exact policy JSON.