fix(ci): publish opencode-plugin via OIDC, mirroring sdk-ts#863
Merged
Conversation
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.
The release workflow's npm auth diverged from the working
release-sdk-ts.yml. sdk-ts publishes via OIDC trusted publishing with the canonical recipe —id-token: write+ setup-noderegistry-url+npm publish --provenance, and no token at all. The original opencode workflow already matched that; it only 404'd because the package didn't exist and the trusted publisher wasn't configured yet — both now done.My two intermediate "fixes" were wrong turns:
registry-url→ENEEDAUTH(npm had no registry context to attempt OIDC).NODE_AUTH_TOKEN: ""and annpm install -g npm@lateststep.This PR
Makes the auth/publish config identical to release-sdk-ts.yml:
id-token: write+registry-url.npm publish --access public --provenance --tag …, noNODE_AUTH_TOKEN, no npm upgrade step.environment:(npm trusted-publisher config has none).After merge I'll re-point
opencode-plugin-v0.1.0-alpha.2so the corrected workflow runs.