([Full Changelog](https://github.com/agoose77/hatch-nodejs-version/compare/v0.3.0...4d3c73d2f4e5ac927274dc810351bc0be95ef224))
Bugs fixed
- Add a trailing newline to package.json when appropriate [17](https://github.com/agoose77/hatch-nodejs-version/pull/17) ([blink1073](https://github.com/blink1073))
Other merged PRs
- Assume NPM person can be string [20](https://github.com/agoose77/hatch-nodejs-version/pull/20) ([vikramaditya91](https://github.com/vikramaditya91))
Contributors to this release
([GitHub contributors page for this release](https://github.com/agoose77/hatch-nodejs-version/graphs/contributors?from=2022-09-21&to=2023-09-06&type=c))
[agoose77](https://github.com/search?q=repo%3Aagoose77%2Fhatch-nodejs-version+involves%3Aagoose77+updated%3A2022-09-21..2023-09-06&type=Issues) | [blink1073](https://github.com/search?q=repo%3Aagoose77%2Fhatch-nodejs-version+involves%3Ablink1073+updated%3A2022-09-21..2023-09-06&type=Issues) | [vikramaditya91](https://github.com/search?q=repo%3Aagoose77%2Fhatch-nodejs-version+involves%3Avikramaditya91+updated%3A2022-09-21..2023-09-06&type=Issues)
<!-- <END NEW CHANGELOG ENTRY> -->
Making a new release of jupyterlab_myst
The extension can be published to `PyPI` and `npm` manually or using the [Jupyter Releaser](https://github.com/jupyter-server/jupyter_releaser).
Manual release
Python package
This extension can be distributed as Python packages. All of the Python
packaging instructions are in the `pyproject.toml` file to wrap your extension in a
Python package. Before generating a package, you first need to install some tools:
bash
pip install build twine hatch
Bump the version using `hatch`. By default this will create a tag.
See the docs on [hatch-nodejs-version](https://github.com/agoose77/hatch-nodejs-version#semver) for details.
bash
hatch version <new-version>
To create a Python source package (`.tar.gz`) and the binary package (`.whl`) in the `dist/` directory, do:
bash
python -m build
> `python setup.py sdist bdist_wheel` is deprecated and will not work for this package.
Then to upload the package to PyPI, do:
bash
twine upload dist/*
NPM package
To publish the frontend part of the extension as a NPM package, do:
bash
npm login
npm publish --access public
Automated releases with the Jupyter Releaser
The extension repository should already be compatible with the Jupyter Releaser.
Check out the [workflow documentation](https://jupyter-releaser.readthedocs.io/en/latest/get_started/making_release_from_repo.html) for more information.
Here is a summary of the steps to cut a new release:
- Add `ADMIN_GITHUB_TOKEN`, `PYPI_TOKEN` and `NPM_TOKEN` to the [Github Secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) in the repository
- Go to the Actions panel
- Run the "Step 1: Prep Release" workflow
- Check the draft changelog
- Run the "Step 2: Publish Release" workflow
Publishing to `conda-forge`
If the package is not on conda forge yet, check the documentation to learn how to add it: https://conda-forge.org/docs/maintainer/adding_pkgs.html
Otherwise a bot should pick up the new version publish to PyPI, and open a new PR on the feedstock repository automatically.