-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
ci: oidc #9764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
ci: oidc #9764
Conversation
🦋 Changeset detectedLatest commit: dc92de6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 22 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
View your CI Pipeline Execution ↗ for commit dc92de6
☁️ Nx Cloud last updated this comment at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This shouldn't have a changeset, since it doesn't actually affect the content of published packages. This also requires specific settings to be enabled by Tanner on NPM.
I thought adding a changeset and releasing a new version would still be fine, since switching to OIDC changes the publishing workflow itself — even if the package content doesn’t. It also helps confirm that the new OIDC-based release flow works as expected.
If the release workflow fails, we can just rerun the changeset workflow after Tanner finishes the NPM configuration to verify everything’s working properly. Hopefully that should confirm the setup. |
No description provided.