Skip to content

Files

Latest commit

21ccbdd · Feb 18, 2023

History

History
50 lines (33 loc) · 1.54 KB

RELEASE.md

File metadata and controls

50 lines (33 loc) · 1.54 KB

Making a new release of quetz server

The quetz server can be published to PyPI manually or using the 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.

pip install build twine

To create a Python source package (.tar.gz) and the binary package (.whl) in the dist/ directory, do:

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:

twine upload dist/*

Automated releases with the Jupyter Releaser

The extension repository should already be compatible with the Jupyter Releaser.

Check out the workflow documentation for more information.

Here is a summary of the steps to cut a new release:

  • Fork the jupyter-releaser repo
  • Add ADMIN_GITHUB_TOKEN and PYPI_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

A bot should pick up the new version publish to PyPI, and open a new PR on the feedstock repository automatically.