Skip to content

Commit f08c893

Browse files
committed
specify with setup-node
1 parent 39bebaa commit f08c893

File tree

3 files changed

+8
-2
lines changed

3 files changed

+8
-2
lines changed

docs/source/get_started/making_release_from_releaser.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,8 @@ already uses Jupyter Releaser.
6969

7070
```yaml
7171
- uses: actions/setup-node@v6
72+
with:
73+
node-version: "24.x"
7274
```
7375
7476
- With Trusted Publishers enabled, npm packages will be published without needing to store an `NPM_TOKEN` secret

docs/source/how_to_guides/convert_repo_from_releaser.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,9 @@ A. Prep the `jupyter_releaser` fork:
7373
Or using the standard `setup-node` action:
7474

7575
```yaml
76-
- uses: actions/setup-node@v4
76+
- uses: actions/setup-node@v6
77+
with:
78+
node-version: "24.x"
7779
```
7880

7981
- With Trusted Publishers enabled, npm packages will be published with provenance automatically, without needing to store an `NPM_TOKEN` secret

docs/source/how_to_guides/convert_repo_from_repo.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,9 @@ See checklist below for details:
6666
Or using the standard `setup-node` action:
6767

6868
```yaml
69-
- uses: actions/setup-node@v4
69+
- uses: actions/setup-node@v6
70+
with:
71+
node-version: "24.x"
7072
```
7173

7274
- With Trusted Publishers enabled, npm packages will be published with provenance automatically, without needing to store an `NPM_TOKEN` secret

0 commit comments

Comments
 (0)