Skip to content

fix(ci): publish opencode-plugin via OIDC, mirroring sdk-ts#863

Merged
ojongerius merged 2 commits into
mainfrom
fix/opencode-plugin-oidc-registry
Jun 16, 2026
Merged

fix(ci): publish opencode-plugin via OIDC, mirroring sdk-ts#863
ojongerius merged 2 commits into
mainfrom
fix/opencode-plugin-oidc-registry

Conversation

@ojongerius

@ojongerius ojongerius commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

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-node registry-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:

This PR

Makes the auth/publish config identical to release-sdk-ts.yml:

  • Keep id-token: write + registry-url.
  • Plain npm publish --access public --provenance --tag …, no NODE_AUTH_TOKEN, no npm upgrade step.
  • No environment: (npm trusted-publisher config has none).

After merge I'll re-point opencode-plugin-v0.1.0-alpha.2 so the corrected workflow runs.

@ojongerius ojongerius changed the title fix(ci): keep registry-url for OIDC, force-clear NODE_AUTH_TOKEN fix(ci): publish opencode-plugin via OIDC, mirroring sdk-ts Jun 16, 2026
@ojongerius ojongerius merged commit a4eb1b6 into main Jun 16, 2026
10 checks passed
@ojongerius ojongerius deleted the fix/opencode-plugin-oidc-registry branch June 16, 2026 04:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant