([Full Changelog](https://github.com/jupyterlite/xeus-lua-kernel/compare/first-commit...47d189ec2368f191401605bdbb1217353cbd635f))
Enhancements made
- using kernel agnostic names [23](https://github.com/jupyterlite/xeus-lua-kernel/pull/23) ([DerThorsten](https://github.com/DerThorsten))
- Fix handling of kernelspec logos [20](https://github.com/jupyterlite/xeus-lua-kernel/pull/20) ([jtpio](https://github.com/jtpio))
- Size [17](https://github.com/jupyterlite/xeus-lua-kernel/pull/17) ([DerThorsten](https://github.com/DerThorsten))
- No more shared-array-buffer [14](https://github.com/jupyterlite/xeus-lua-kernel/pull/14) ([DerThorsten](https://github.com/DerThorsten))
Bugs fixed
- Fix Check Release job on CI [12](https://github.com/jupyterlite/xeus-lua-kernel/pull/12) ([jtpio](https://github.com/jtpio))
- copy wasm file via plugin [10](https://github.com/jupyterlite/xeus-lua-kernel/pull/10) ([DerThorsten](https://github.com/DerThorsten))
Maintenance and upkeep improvements
- Update package name and cleanup [26](https://github.com/jupyterlite/xeus-lua-kernel/pull/26) ([jtpio](https://github.com/jtpio))
- Update links after the move to the org [25](https://github.com/jupyterlite/xeus-lua-kernel/pull/25) ([jtpio](https://github.com/jtpio))
- pinning the repos in the Dockerfile [22](https://github.com/jupyterlite/xeus-lua-kernel/pull/22) ([DerThorsten](https://github.com/DerThorsten))
- More cleanup [21](https://github.com/jupyterlite/xeus-lua-kernel/pull/21) ([jtpio](https://github.com/jtpio))
- Cleanup webpack.config.js [19](https://github.com/jupyterlite/xeus-lua-kernel/pull/19) ([jtpio](https://github.com/jtpio))
- Upload the releaser distributions as artifacts [18](https://github.com/jupyterlite/xeus-lua-kernel/pull/18) ([jtpio](https://github.com/jtpio))
- minor fixes [15](https://github.com/jupyterlite/xeus-lua-kernel/pull/15) ([DerThorsten](https://github.com/DerThorsten))
- Remove unused files [13](https://github.com/jupyterlite/xeus-lua-kernel/pull/13) ([jtpio](https://github.com/jtpio))
- Build the extension [6](https://github.com/jupyterlite/xeus-lua-kernel/pull/6) ([jtpio](https://github.com/jtpio))
- Troubleshoot build issues [3](https://github.com/jupyterlite/xeus-lua-kernel/pull/3) ([jtpio](https://github.com/jtpio))
- added webpack config [2](https://github.com/jupyterlite/xeus-lua-kernel/pull/2) ([DerThorsten](https://github.com/DerThorsten))
Contributors to this release
([GitHub contributors page for this release](https://github.com/jupyterlite/xeus-lua-kernel/graphs/contributors?from=2021-10-04&to=2021-10-22&type=c))
[DerThorsten](https://github.com/search?q=repo%3Ajupyterlite%2Fxeus-lua-kernel+involves%3ADerThorsten+updated%3A2021-10-04..2021-10-22&type=Issues) | [jtpio](https://github.com/search?q=repo%3Ajupyterlite%2Fxeus-lua-kernel+involves%3Ajtpio+updated%3A2021-10-04..2021-10-22&type=Issues)
Making a new release of jupyterlite_xeus_lua
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 in the `pyproject.toml` file to wrap your extension in a
Python package. Before generating a package, we first need to install `build`.
bash
pip install build twine
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://github.com/jupyter-server/jupyter_releaser#typical-workflow) for more information.
Here is a summary of the steps to cut a new release:
- Fork the [`jupyter-releaser` repo](https://github.com/jupyter-server/jupyter_releaser)
- Add `ADMIN_GITHUB_TOKEN`, `PYPI_TOKEN` and `NPM_TOKEN` to the Github Secrets in the fork
- Go to the Actions panel
- Run the "Draft Changelog" workflow
- Merge the Changelog PR
- Run the "Draft Release" workflow
- Run the "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.