Repository navigation
ci: remove temporary npm/OIDC publish diagnostics - #235
Merged
Merged
Conversation
The diagnostic confirmed the CI side is correct: npm 11.14.1 (OIDC-capable), both ACTIONS_ID_TOKEN_REQUEST_* env vars present, registry registry.npmjs.org — yet publish still fails ENEEDAUTH. The cause is registry-side (the geist Trusted Publisher config on npmjs.org), not the workflow, so the diagnostic has served its purpose.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
Removes the temporary diagnostic step added in #234.
It did its job — confirmed the CI side is correct (npm 11.14.1 / OIDC-capable, both
ACTIONS_ID_TOKEN_REQUEST_*env vars present, registryregistry.npmjs.org), yetgeist@1.7.2still failsENEEDAUTH. So the cause is registry-side — thegeistTrusted Publisher config on npmjs.org (tracked via #help-it), not the workflow.Safe to merge anytime; ideally after the npm-side fix is confirmed so we keep the diagnostic available if we need another run.