1
- # Making a new release of jupyter-resource-usage
1
+ # Making a new release of ` jupyter-resource-usage `
2
2
3
3
## Getting a clean environment
4
4
5
5
Creating a new environment can help avoid pushing local changes and any extra tag.
6
6
7
7
``` bash
8
- conda create -n jupyter-resource-usage-release -c conda-forge twine keyring jupyter-packaging python
8
+ mamba create -n jupyter-resource-usage-release -c conda-forge twine keyring jupyter-packaging=0.7 jupyterlab=3 python
9
9
conda activate jupyter-resource-usage-release
10
-
11
- # install JupyterLab to build the extension
12
- python -m pip install --pre jupyterlab
13
10
```
14
11
15
12
Alternatively, the local repository can be cleaned with:
@@ -23,13 +20,14 @@ git clean -fdx
23
20
Make sure the ` dist/ ` folder is empty.
24
21
25
22
1 . Update the version in ` setup.py `
26
- 2 . ` python setup.py sdist bdist_wheel `
27
- 3 . Double check the size of the bundles in the ` dist/ ` folder
28
- 4 . Run the tests
23
+ 2 . If the JupyterLab extension has changed, make sure to bump the version number in ` packages/labextension/package.json `
24
+ 3 . ` python setup.py sdist bdist_wheel `
25
+ 4 . Double check the size of the bundles in the ` dist/ ` folder
26
+ 5 . Run the tests
29
27
- ` pip install "dist/jupyter-resource-usage-X.Y.Z-py3-none-any.whl[dev]" `
30
28
- ` python -m pytest `
31
- 5 . ` export TWINE_USERNAME=mypypi_username `
32
- 6 . ` twine upload dist/* `
29
+ 6 . ` export TWINE_USERNAME=mypypi_username `
30
+ 7 . ` twine upload dist/* `
33
31
34
32
## Releasing on conda-forge
35
33
0 commit comments