Repository navigation
npm-trusted-publishing-stable - #881
Closed
jeffreyaven wants to merge 1 commit into
Closed
jeffreyaven wants to merge 1 commit into
jeffreyaven wants to merge 1 commit into
Conversation
Publish @stackql/mcp-server from the mcp-packaging workflow via npm trusted publishing (GitHub Actions OIDC, provenance attached) instead of a local npm login + OTP publish. Adds the idempotent make npm-publish target (publishes the same npm/ directory that npm-pack packs) and the npm-publish job gated like the other sdk publish jobs. PyPI stays manual. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> (cherry picked from commit 70c09ea)
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.
Description
Cherry-pick of #880 (
70c09ea, applied with-x, zero conflicts) ontostable/v0.13, so that thev0.13.xrelease dispatched from this branch publishes@stackql/mcp-serverthrough thenpm-publishjob (npm trusted publishing, GitHub Actions OIDC, provenance attached) rather than a localnpm login+ OTP publish.mcp-packagingis run withworkflow_dispatchfrom the branch being released, so the job must exist onstable/v0.13, not only onmain. The npm trusted publisher configuration (ownerstackql, repostackql, workflowmcp-packaging.yml,npm publishallowed) has no branch restriction, so no npmjs.com change is needed.Same five files as #880:
packaging/mcpb/Makefile(newnpm-publishtarget),.github/workflows/mcp-packaging.yml(newnpm-publishjob),.github/workflows/mcp-registry-publish.yml(comments),packaging/mcpb/README.md,docs/stackql_release_process.md. No change tonpm/package.json,bin/stackql-mcp.js, renderer scripts, or the PyPI / cargo / go / dotnet / OCI / registry jobs.Type of change
Issues referenced.
#880
Evidence
git cherry-pick -x 70c09eaontoorigin/stable/v0.13(6023b6c): applied cleanly;git diff --stat origin/stable/v0.13 origin/main -- <five files>before the pick was exactly the npm-trusted-publishing #880 diff (73+/23-), so the branches were otherwise identical for these files.main: both workflow YAMLs parsed,make -n npm-publish VERSION=0.0.0dry run printed the expected recipe chain, themcp-packagingPR run was green withpublish npm (@stackql/mcp-server)correctly skipped (is_publish != 'true').mcp-packagingPR validation on this PR exercises the same jobs on this branch.npm publish, workflow dispatch. The first OIDC publish is thev0.13.xrelease dispatched fromstable/v0.13.Checklist:
Variations
No Go code, robot tests, or unit tests are affected (CI workflow, Makefile and docs only); the unit / robot / lint items are not applicable. Validation is the
mcp-packagingPR check on this branch plus the dry-run evidence from #880.Tech Debt
None. Identical content to
main; no divergence introduced between the branches for these files.