Skip to content

npm-trusted-publishing-stable - #881

Closed
jeffreyaven wants to merge 1 commit into
stable/v0.13from
chore/npm-trusted-publishing-stable
Closed

jeffreyaven wants to merge 1 commit into
stable/v0.13from
chore/npm-trusted-publishing-stable

Conversation

@jeffreyaven

Copy link
Copy Markdown
Member

Description

Cherry-pick of #880 (70c09ea, applied with -x, zero conflicts) onto stable/v0.13, so that the v0.13.x release dispatched from this branch publishes @stackql/mcp-server through the npm-publish job (npm trusted publishing, GitHub Actions OIDC, provenance attached) rather than a local npm login + OTP publish.

mcp-packaging is run with workflow_dispatch from the branch being released, so the job must exist on stable/v0.13, not only on main. The npm trusted publisher configuration (owner stackql, repo stackql, workflow mcp-packaging.yml, npm publish allowed) has no branch restriction, so no npmjs.com change is needed.

Same five files as #880: packaging/mcpb/Makefile (new npm-publish target), .github/workflows/mcp-packaging.yml (new npm-publish job), .github/workflows/mcp-registry-publish.yml (comments), packaging/mcpb/README.md, docs/stackql_release_process.md. No change to npm/package.json, bin/stackql-mcp.js, renderer scripts, or the PyPI / cargo / go / dotnet / OCI / registry jobs.

Type of change

  • Bug fix (non-breaking change to fix a bug).
  • Feature (non-breaking change to add functionality).
  • Breaking change.
  • Other (eg: documentation change). Please explain. CI / release-process change, backport of npm-trusted-publishing #880 to the stable branch.

Issues referenced.

#880

Evidence

  • git cherry-pick -x 70c09ea onto origin/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.
  • On npm-trusted-publishing #880 against main: both workflow YAMLs parsed, make -n npm-publish VERSION=0.0.0 dry run printed the expected recipe chain, the mcp-packaging PR run was green with publish npm (@stackql/mcp-server) correctly skipped (is_publish != 'true').
  • The mcp-packaging PR validation on this PR exercises the same jobs on this branch.
  • Not run: npm publish, workflow dispatch. The first OIDC publish is the v0.13.x release dispatched from stable/v0.13.

Checklist:

  • A full round of testing has been completed, and there are no test failures as a result of these changes.
  • The changes are covered with functional and/or integration robot testing.
  • The changes work on all supported platforms.
  • Unit tests pass locally, as per the developer guide.
  • Robot tests pass locally, as per the developer guide.
  • Linter passes locally, as per the developer guide.

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-packaging PR 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.

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)
@general-kroll-4-life
general-kroll-4-life changed the base branch from stable/v0.13 to main November 2, 2026 08:15
@general-kroll-4-life
general-kroll-4-life changed the base branch from main to stable/v0.13 November 2, 2026 08:15
@jeffreyaven
jeffreyaven deleted the chore/npm-trusted-publishing-stable branch November 4, 2026 20:49
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.

2 participants