1- # Making a new release of jupyter-resource-usage
1+ # Making a new release of ` jupyter-resource-usage `
22
33## Getting a clean environment
44
55Creating a new environment can help avoid pushing local changes and any extra tag.
66
77``` 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
99conda activate jupyter-resource-usage-release
10-
11- # install JupyterLab to build the extension
12- python -m pip install --pre jupyterlab
1310```
1411
1512Alternatively, the local repository can be cleaned with:
@@ -23,13 +20,14 @@ git clean -fdx
2320Make sure the ` dist/ ` folder is empty.
2421
25221 . 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
2927 - ` pip install "dist/jupyter-resource-usage-X.Y.Z-py3-none-any.whl[dev]" `
3028 - ` 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/* `
3331
3432## Releasing on conda-forge
3533
0 commit comments