Skip to content

Refresh README and trust publisher setup guidance #3

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
Markeljan merged 1 commit into from
Mar 5, 2026
Merged

Refresh README and trust publisher setup guidance #3

Show file tree
Hide file tree
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
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,7 @@ jobs:
- name: Setup Node (for npm publish)
uses: actions/setup-node@v4
with:
node-version: 20
registry-url: https://registry.npmjs.org
node-version: 22

- name: Setup Bun
uses: oven-sh/setup-bun@v2
Expand All @@ -51,3 +50,4 @@ jobs:
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_CONFIG_PROVENANCE: true
NODE_AUTH_TOKEN: ""
1 change: 1 addition & 0 deletions docs/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ This repository uses [Changesets](https://github.com/changesets/changesets) for
1. In npm package settings, enable Trusted Publishing for this GitHub repository/workflow.
2. Keep `main` protected (require PRs and green CI before merge).
3. No `NPM_TOKEN` secret is required when Trusted Publishing is configured correctly.
4. Release workflow uses Node 22 and explicitly clears `NODE_AUTH_TOKEN` to avoid token fallback auth.

## Daily release workflow

Expand Down