Release instructions

Information about releasing new versions of Slycot.

Tag the relevant release as vMAJOR.MINOR.PATCH. Pushing this tag will trigger a build action generating the sdist and wheels. Add release notes in Github (see template at end).

Upload the sdist and wheels generated by GitHub Actions to PyPI (see below).

Notify conda-forge packagers (see https://github.com/conda-forge/slycot-feedstock/).

PyPI

To upload a new version to PyPI, you need to use twine. See Python packaging tutorial for information on how to do this.

As of v0.7.0, all the necessary files to upload are generated by the cibuildwheel action; once this action has completed, scroll to the end and download all the ZIP files (e.g., cibw-wheels-macos-14-4.zip) and the sdist (e.g., slycot-0.7.0.tar.gz).

Unpack the zip files, and upload all wheel files (e.g., slycot-0.7.0-cp314-cp314-win_amd64.whl) and the sdist to PyPI using twine.

Release notes

Release notes are written in Markdown, and follow the template below.

# Highlights and important notes
# New features
# Fixes
# Build
# Testing
# Other changes
# Pull requests and issues associated with the release

PRs merged: #
Issues fixed: #
Issues closed ("wont-fix"): #