You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE.md
+4-6
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Using `jupyter_releaser`
4
4
5
-
The recommended way to make a release is to use [`jupyter_releaser`](https://github.com/jupyter-server/jupyter_releaser#checklist-for-adoption).
5
+
The recommended way to make a release is to use [`jupyter_releaser`](https://jupyter-releaser.readthedocs.io/en/latest/get_started/making_release_from_repo.html).
6
6
7
7
Note that we must use manual versions since Jupyter Releaser does not
8
8
yet support "next" or "patch" when dev versions are used.
@@ -14,19 +14,17 @@ To create a manual release, perform the following steps:
14
14
### Set up
15
15
16
16
```bash
17
-
pip install hatchling twine build
17
+
pip install hatch twine build
18
18
git pull origin $(git branch --show-current)
19
19
git clean -dffx
20
-
npm install
21
-
npm run build
22
20
```
23
21
24
22
### Update the version and apply the tag
25
23
26
24
```bash
27
25
echo"Enter new version"
28
26
read new_version
29
-
hatchling version ${new_version}
27
+
hatch version ${new_version}
30
28
git tag -a ${new_version} -m "Release ${new_version}"
0 commit comments