Jupyterlab-gridwidth

Latest version: v0.4.3

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

0.1.3

- merged 4 - keyboard shortcuts are now in the form
Alt-1 Alt-2 etc, or just Alt-0
thanks firezym

0.1.2

- expose command `split-cell-to-gridwidth` to convert notebooks

0.1.1

- initial release


Making a new release of jupyterlab_gridwidth

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.

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.