Skip to content

refactor: publish to npm via GitHub Actions - #678

Draft
wesleyboar wants to merge 4 commits into
mainfrom
ci/npm-publish-oidc
Draft

refactor: publish to npm via GitHub Actions#678
wesleyboar wants to merge 4 commits into
mainfrom
ci/npm-publish-oidc

Conversation

@wesleyboar

@wesleyboar wesleyboar commented Jul 31, 2026

Copy link
Copy Markdown
Member

Overview

Moves npm publish out of bin/release.sh in to new GitHub Actions workflow that runs when a GitHub release is created (authenticating via npm Trusted Publishing (OIDC) instead of a long-lived npm token).

Caution

Untested!

Related

Changes

  • added workflow for npm publish
  • changed release script (no npm actions)
  • updated PUBLISHING.md

Testing

  1. bash -n bin/release.sh — syntax check passes
  2. Publish a test release ...-rc….
  3. Verify release succeeds.
  4. Verify process performs all things previous release process does.

Notes

Tip

Prerequisite (manual, on npmjs.com) of registering TACC/Core-Styles and npm-publish.yml as a Trusted Publisher for @tacc/core-styles is completed.

Move npm publish out of the local release script and into a GitHub
Actions workflow triggered on release creation, authenticating via
npm Trusted Publishing (OIDC) instead of a long-lived token.
- release.sh no longer checks npm login or runs npm publish locally
- requires one-time npm Trusted Publisher registration for this repo/workflow

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

wesleyboar and others added 3 commits July 31, 2026 17:07
Match structure, action versions, and node version used by
Core-Components' npm-publish.yml as closely as possible.
- add publishConfig.access:public to package.json so npm publish
  needs no --access flag, same as Core-Components
- drop the redundant npm@latest upgrade step (unneeded per
  Core-Components' working setup)
- keep the rc/latest dist-tag step and skip npm test/build, both
  currently-necessary differences from Core-Components

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@wesleyboar
wesleyboar marked this pull request as draft July 31, 2026 22:29
@wesleyboar wesleyboar changed the title ci(release): publish to npm via GitHub Actions using OIDC refactor: publish to npm via GitHub Actions using OIDC Jul 31, 2026
@wesleyboar wesleyboar changed the title refactor: publish to npm via GitHub Actions using OIDC refactor: publish to npm via GitHub Actions Jul 31, 2026
@wesleyboar wesleyboar added the refactor Re-writes/structures code but retains behavior label Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactor Re-writes/structures code but retains behavior

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant