ci: remove environment from release job to fix OIDC trust policy mismatch#39
Merged
SamuelSSalazar merged 1 commit intomasterfrom Mar 16, 2026
Merged
Conversation
CharlesRea
approved these changes
Mar 16, 2026
Contributor
|
🎉 This PR is included in version 7.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By submitting a PR to this repository, I agree to the terms within the Auth0 Code of Conduct.
Description
Removed
environment: releasefrom the release workflow. All secrets used in this workflow are defined at the org level, no secrets are scoped to the environment.Why?
The
releaseworkflow is failing withNot authorized to perform sts:AssumeRoleWithWebIdentity.When a GitHub Actions job specifies an
environment, the OIDC token'ssubclaim changes fromrepo:auth0/node-wsfed:ref:refs/heads/mastertorepo:auth0/node-wsfed:environment:release. The IAM trust policy was configured with theref-based claim, causing the mismatch.Checklist