Skip to content

fix(🐙): enable automated npm publishing via semantic-release #398

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
wcandillon merged 8 commits into from
Jun 28, 2026
Merged

fix(🐙): enable automated npm publishing via semantic-release #398

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
35f0dd6
:wrench:
wcandillon Jun 28, 2026
851a547
:wrench:
wcandillon Jun 28, 2026
dcecaae
chore(🐙): update node for npm publishing
wcandillon Jun 28, 2026
2d9b38d
Merge branch 'main' into publishing
wcandillon Jun 28, 2026
2a496f0
fix(🐙): enable automated npm publishing via semantic-release
wcandillon Jun 28, 2026
451caf7
Merge branch 'publishing' of https://github.com/wcandillon/react-nati…
wcandillon Jun 28, 2026
30aa0e7
Change Node version to 24 for npm publishing
wcandillon Jun 28, 2026
e1ed17f
Merge branch 'main' into publishing
wcandillon Jun 28, 2026
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: 0 additions & 4 deletions .github/workflows/publish-npm.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,10 +24,6 @@ jobs:
with:
github_token: ${{ secrets.GITHUB_TOKEN }}

# Tokenless trusted publishing needs npm >= 11.5.1. The repo's .nvmrc
# pins Node 22 (npm 10), and `npm install -g npm@latest` self-upgrade is
# broken on that npm (MODULE_NOT_FOUND 'promise-retry'). So switch the
# publish steps to Node 24, which already bundles npm 11.6+.
- name: Use Node with npm 11+
uses: actions/setup-node@v4
with:
Expand Down
Loading