ci(evaluation): publish typescript package with npm oidc - #2754
Merged
Conversation
Replace token-based npm authentication with a manual trusted-publishing workflow and document the release process. Co-authored-by: Cursor <cursoragent@cursor.com>
cre8ivejp
marked this pull request as ready for review
August 7, 2026 02:25
There was a problem hiding this comment.
Pull request overview
Adds a manual GitHub Actions workflow to publish the @bucketeer/evaluation TypeScript package to npm using trusted publishing (OIDC), removing the legacy NPM_TOKEN-based flow and documenting the new release process.
Changes:
- Add
workflow_dispatchpublish workflow that uses npm OIDC trusted publishing and supports adry_runoption. - Remove
NPM_TOKENusage/configuration from the TypeScript evaluation package and CI. - Bump
@bucketeer/evaluationto0.0.9and restrict published contents viafilesinpackage.json.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
evaluation/typescript/README.md |
Updates setup/release documentation to describe the new manual publish workflow (OIDC) and removes token-based instructions. |
evaluation/typescript/package.json |
Bumps version to 0.0.9, sets publishConfig.access, and restricts published files. |
evaluation/typescript/.npmrc |
Removes legacy token-based npm authentication configuration. |
.github/workflows/publish-evaluation-ts.yaml |
Adds a manual workflow to build and publish the package to npm via OIDC trusted publishing (with optional dry run). |
.github/workflows/pr-evaluation-ts.yaml |
Removes NPM_TOKEN from the PR workflow environment configuration. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Cursor <cursoragent@cursor.com>
The evaluation package now uses a manual publishing workflow, while the repository release workflow only reads the root release-please configuration. Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Suppressed comments (1)
.github/workflows/publish-evaluation-ts.yaml:9
dry_rundefaults tofalse, so clicking “Run workflow” will publish immediately unless the user changes the input. To reduce the chance of accidental releases, consider defaultingdry_runtotrueand requiring an explicit opt-in to publish.
dry_run:
description: "Dry run (do not actually publish)"
required: false
default: false
type: boolean
Prevent manual workflow dispatches from publishing unmerged branch contents. Co-authored-by: Cursor <cursoragent@cursor.com>
cre8ivejp
enabled auto-merge (squash)
August 7, 2026 02:43
cre8ivejp
disabled auto-merge
August 7, 2026 02:43
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.
Fix #2755
Summary
@bucketeer/evaluationusing npm trusted publishingNPM_TOKENconfiguration0.0.9and restrict published filesTest plan
npm publish --dry-rundry_runenabled after merge**