mirror/notebook
2
0
Fork 0
mirror of https://github.com/jupyter/notebook.git synced 2024-11-27 03:20:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update release instructions

Browse Source
This commit is contained in:
Jeremy Tuloup 2021-01-13 10:44:04 +01:00 committed by GitHub
parent 582c85015d
commit f3af4cc73c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
RELEASE.md
View File

@ -9,7 +9,7 @@ This should normally be possible to automate the process at some point.
Creating a new environment can help avoid pushing local changes and any extra tag.
```bash
mamba create -q -y -n jupyterlab-classic-release -c conda-forge twine nodejs -y
mamba create -q -y -n jupyterlab-classic-release -c conda-forge twine nodejs jupyter-packaging jupyterlab -y
conda activate jupyterlab-classic-release
```
@ -24,16 +24,19 @@ git clean -fdx
Make sure the `dist/` folder is empty.
1. Update [jupyterlab_classic/\_version.py](./jupyterlab_classic/_version.py) with the new version number
2. Run: `python setup.py sdist bdist_wheel`
3. Double check the size of the bundles in the `dist/` folder
4. Test the release by installing the wheel or sdist: `python -m pip install ./dist/jupyterlab_classic-0.1.1-py3-none-any.whl
5. Commit the changes
2. Commit the changes
- `git add jupyterlab_classic/_version.py`
- `git commit -m "Release x.y.z"`
- `git add jupyterlab_classic/_version.py`
- `git commit -m "Release x.y.z"`
3. Bump the frontend packages:
5. `export TWINE_USERNAME=mypypi_username`
6. `twine upload dist/*`
- `jlpm`
- `jlpm run lerna version x.y.z --no-push --amend --force-publish`
4. Run: `python setup.py sdist bdist_wheel`
5. Double check the size of the bundles in the `dist/` folder
6. Test the release by installing the wheel or sdist: `python -m pip install ./dist/jupyterlab_classic-x.y.z-py3-none-any.whl
7. `export TWINE_USERNAME=mypypi_username`
8. `twine upload dist/*`
## Releasing on conda-forge
@ -49,9 +52,7 @@ The new version will be available on `conda-forge` soon after.
## Publish the packages to npm
1. Bump the version in
2. `jlpm run lerna version x.y.z --no-push --amend --force-publish`
3. `jlpm run lerna publish from-package`
1. Publish the packages: `jlpm run lerna publish from-package`
## Committing and tagging