Skip to content

fix: trusted publishing 3 #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jkadamczyk merged 1 commit into from
Jan 26, 2026
Merged

fix: trusted publishing 3 #23

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,6 @@ jobs:
env:
# Force npm to emit provenance (SLSA) when publishing via OIDC.
NPM_CONFIG_PROVENANCE: true
NODE_AUTH_TOKEN: ${{ secrets.NPM_PUBLISH_TOKEN_PHANTOM_SECURITY_BOT }}

steps:
- name: Checkout Repo
Expand All @@ -33,8 +32,8 @@ jobs:
uses: actions/setup-node@v4
with:
node-version: 20.x
cache: "yarn"
registry-url: "https://registry.npmjs.org"
token: ${{ secrets.NPM_PUBLISH_TOKEN_PHANTOM_SECURITY_BOT }}

- name: Ensure npm 11.5.1+ for trusted publishing
run: npm install -g npm@^11.5.1
Expand All @@ -44,10 +43,11 @@ jobs:

- name: Create Release Pull Request or Publish to npm
id: changesets
uses: changesets/action@v1
uses: changesets/action@e0145edc7d9d8679003495b11f87bd8ef63c0cba
with:
# This expects you to have a script called release which does a build for your packages and calls changeset publish
version: yarn changeset version
publish: yarn release
commitMode: github-api
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_PUBLISH_TOKEN_PHANTOM_SECURITY_BOT }}
Loading