Skip to content

Commit bd702be

Browse files
committed
cleanup
1 parent 797c1f5 commit bd702be

File tree

3 files changed

+0
-6
lines changed

3 files changed

+0
-6
lines changed

docs/source/get_started/making_release_from_releaser.md

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

7272
```yaml
7373
- uses: actions/setup-node@v6
74-
with:
75-
node-version: "24"
7674
```
7775
7876
- 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: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,6 @@ A. Prep the `jupyter_releaser` fork:
7676

7777
```yaml
7878
- uses: actions/setup-node@v4
79-
with:
80-
node-version: "24"
8179
```
8280

8381
- 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: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -69,8 +69,6 @@ See checklist below for details:
6969

7070
```yaml
7171
- uses: actions/setup-node@v4
72-
with:
73-
node-version: "24"
7472
```
7573

7674
- 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)