Skip to content

fix(publish): npmjs OIDC trusted publishing (match ui/i18n/legal) - #1

Merged
ditto-m[bot] merged 2 commits into
mainfrom
fix/npmjs-trusted-publish
Jun 29, 2026
Merged

ditto-m[bot] merged 2 commits into
mainfrom
fix/npmjs-trusted-publish

Conversation

@ditto-m

@ditto-m ditto-m Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

feature-gate is the last public lib not yet on public npmjs (@etamong-playground/{ui,i18n,legal} are live). This adopts the same proven publish workflow:

  • Canonical = public npmjs.com via GitHub Actions OIDC Trusted Publishing — token-less, provenance-attested (id-token: write + npm publish --access public, no registry-url).
  • GitHub Packages = mirror (built-in GITHUB_TOKEN).
  • Removes the dead Forgejo publish branch + NPM_PUBLISH_TOKEN/GITHUB_SERVER_URL detection + the runtime npm pkg set name/delete publishConfig mutation (name is already correct).
  • Adds publishConfig.access=public to package.json.

Operator one-time (npmjs account): configure a Trusted Publisher for @etamong-playground/feature-gate (repo etamong-playground/feature-gate, workflow publish.yml), then push a v*.*.* tag — the OIDC publish then lands it on npmjs (creating the package). Until then this is inert; nothing breaks (current GH Packages consumers unaffected).

Relates to the npm→npmjs migration.

feature-gate is the last public lib not on npmjs. Adopt the fleet's
proven publish workflow: canonical = public npmjs.com via GitHub Actions
OIDC Trusted Publishing (token-less, provenance), GitHub Packages kept as
mirror. Drop the dead Forgejo publish branch + the runtime name/publishConfig
mutation (name is already @etamong-playground/feature-gate). Add
publishConfig.access=public.

Operator one-time: configure the npmjs Trusted Publisher for
@etamong-playground/feature-gate, then tag to publish.
@ditto-m
ditto-m Bot requested a review from a team as a code owner June 29, 2026 12:49
@ditto-m
ditto-m Bot merged commit d20c938 into main Jun 29, 2026
1 check passed
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.

0 participants