Skip to content

MILAB-7081: release all packages via npm trusted publishing - #28

Merged
mike-ainsel merged 2 commits into
mainfrom
MILAB-7081_npm-trusted-publishing-release
Oct 20, 2026
Merged

mike-ainsel merged 2 commits into
mainfrom
MILAB-7081_npm-trusted-publishing-release

Conversation

@mike-ainsel

@mike-ainsel mike-ainsel commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Adds one changeset that bumps every package of the repository (patch; model/ui/workflow/test included, .kind untouched), so the next release publishes all of them through npm trusted publishing (OIDC).

Why: npm stopped accepting the 2FA-bypass NPMJS_TOKEN; this repo already publishes via node-simple-pnpm.yaml@v4 (pack on our runner, upload from a GitHub-hosted job). A new trusted publisher on npmjs.com expires unless a publish goes through it within 2 days, and a release only publishes the packages its changesets bump — so every package needs one release now.

Merge only after the trusted publishers for these packages are configured (infra/npm-trust/npm-trust-setup.sh apply), and within 2 days of that.

No code changes.

Minor bump for every public package so each one publishes once through its new npm trusted publisher (OIDC), which expires unless used within 2 days.
@greptile-apps

greptile-apps Bot commented Oct 20, 2026

Copy link
Copy Markdown

No reviewable files after applying ignore patterns.

Patch instead of minor, and bump model/ui/workflow/test together with the published packages, as block changesets usually do. The .kind package stays untouched.
@mike-ainsel
mike-ainsel merged commit 2212f7a into main Oct 20, 2026
13 checks passed
@mike-ainsel
mike-ainsel deleted the MILAB-7081_npm-trusted-publishing-release branch October 20, 2026 15:48
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