Releasing a version#

The following guides include detailed information on how to prepare a NumPy release.

How to prepare a release#

These instructions give an overview of what is necessary to build binary releases for NumPy.

Current build and release info#

Useful info can be found in the following locations:

Supported platforms and versions#

NEP 29 outlines which Python versions are supported; For the first half of 2020, this will be Python >= 3.6. We test NumPy against all these versions every time we merge code to main. Binary installers may be available for a subset of these versions (see below).

  • OS X

    OS X versions >= 10.9 are supported, for Python version support see NEP 29. We build binary wheels for OSX that are compatible with Python.org Python, system Python, homebrew and macports - see this OSX wheel building summary for details.

  • Windows

    We build 32- and 64-bit wheels on Windows. Windows 7, 8 and 10 are supported. We build NumPy using the mingw-w64 toolchain, cibuildwheels and GitHub actions.

  • Linux

    We build and ship manylinux2014 wheels for NumPy. Many Linux distributions include their own binary builds of NumPy.

  • BSD / Solaris

    No binaries are provided, but successful builds on Solaris and BSD have been reported.

Tool chain#

We build all our wheels on cloud infrastructure - so this list of compilers is for information and debugging builds locally. See the .travis.yml script in the numpy wheels repo for an outdated source of the build recipes using multibuild.

Compilers#

The same gcc version is used as the one with which Python itself is built on each platform. At the moment this means:

  • OS X builds on travis currently use clang. It appears that binary wheels for OSX >= 10.6 can be safely built from the travis-ci OSX 10.9 VMs when building against the Python from the Python.org installers;

  • Windows builds use the mingw-w64 toolchain;

  • Manylinux2014 wheels use the gcc provided on the Manylinux docker images.

You will need Cython for building the binaries. Cython compiles the .pyx files in the NumPy distribution to .c files.

OpenBLAS#

All the wheels link to a version of OpenBLAS supplied via the openblas-libs repo. The shared object (or DLL) is shipped with in the wheel, renamed to prevent name collisions with other OpenBLAS shared objects that may exist in the filesystem.

Building source archives and wheels#

The NumPy wheels and sdist are now built using cibuildwheel with github actions.

Building docs#

We are no longer building PDF files. All that will be needed is

  • virtualenv (pip).

The other requirements will be filled automatically during the documentation build process.

Uploading to PyPI#

The only application needed for uploading is

  • twine (pip).

You will also need a PyPI token, which is best kept on a keyring. See the twine keyring documentation for how to do that.

Generating author/PR lists#

You will need a personal access token https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/ so that scripts can access the github NumPy repository.

  • gitpython (pip)

  • pygithub (pip)

What is released#

  • Wheels We currently support Python 3.8-3.10 on Windows, OSX, and Linux.

    • Windows: 32-bit and 64-bit wheels built using Github actions;

    • OSX: x64_86 and arm64 OSX wheels built using Github actions;

    • Linux: x64_86 and aarch64 Manylinux2014 wheels built using Github actions.

  • Other Release notes and changelog

  • Source distribution We build source releases in the .tar.gz format.

Release process#

Agree on a release schedule#

A typical release schedule is one beta, two release candidates and a final release. It’s best to discuss the timing on the mailing list first, in order for people to get their commits in on time, get doc wiki edits merged, etc. After a date is set, create a new maintenance/x.y.z branch, add new empty release notes for the next version in the main branch and update the Trac Milestones.

Make sure current branch builds a package correctly#

The CI builds wheels when a PR header begins with REL. Your last PR before releasing should be so marked and all the tests should pass. You can also do:

git clean -fxdq
python setup.py bdist_wheel
python setup.py sdist

For details of the build process itself, it is best to read the Step-by-Step Directions below.

Note

The following steps are repeated for the beta(s), release candidates(s) and the final release.

Check deprecations#

Before the release branch is made, it should be checked that all deprecated code that should be removed is actually removed, and all new deprecations say in the docstring or deprecation warning what version the code will be removed.

Check the C API version number#

The C API version needs to be tracked in three places

  • numpy/_core/meson.build

  • numpy/_core/code_generators/cversions.txt

  • numpy/_core/include/numpy/numpyconfig.h

There are three steps to the process.

  1. If the API has changed, increment the C_API_VERSION in numpy/core/meson.build. The API is unchanged only if any code compiled against the current API will be backward compatible with the last released NumPy version. Any changes to C structures or additions to the public interface will make the new API not backward compatible.

  2. If the C_API_VERSION in the first step has changed, or if the hash of the API has changed, the cversions.txt file needs to be updated. To check the hash, run the script numpy/_core/cversions.py and note the API hash that is printed. If that hash does not match the last hash in numpy/_core/code_generators/cversions.txt the hash has changed. Using both the appropriate C_API_VERSION and hash, add a new entry to cversions.txt. If the API version was not changed, but the hash differs, you will need to comment out the previous entry for that API version. For instance, in NumPy 1.9 annotations were added, which changed the hash, but the API was the same as in 1.8. The hash serves as a check for API changes, but it is not definitive.

    If steps 1 and 2 are done correctly, compiling the release should not give a warning “API mismatch detect at the beginning of the build”.

  3. The numpy/_core/include/numpy/numpyconfig.h will need a new NPY_X_Y_API_VERSION macro, where X and Y are the major and minor version numbers of the release. The value given to that macro only needs to be increased from the previous version if some of the functions or macros in the include files were deprecated.

The C ABI version number in numpy/_core/meson.build should only be updated for a major release.

Check the release notes#

Use towncrier to build the release note and commit the changes. This will remove all the fragments from doc/release/upcoming_changes and add doc/release/<version>-note.rst.:

towncrier build --version "<version>"
git commit -m"Create release note"

Check that the release notes are up-to-date.

Update the release notes with a Highlights section. Mention some of the following:

  • major new features

  • deprecated and removed features

  • supported Python versions

  • for SciPy, supported NumPy version(s)

  • outlook for the near future

Step-by-step directions#

This is a walkthrough of the NumPy 2.1.0 release on Linux, modified for building with GitHub Actions and cibuildwheels and uploading to the anaconda.org staging repository for NumPy. The commands can be copied into the command line, but be sure to replace 2.1.0 by the correct version. This should be read together with the general release guide.

Facility preparation#

Before beginning to make a release, use the requirements/*_requirements.txt files to ensure that you have the needed software. Most software can be installed with pip, but some will require apt-get, dnf, or whatever your system uses for software. You will also need a GitHub personal access token (PAT) to push the documentation. There are a few ways to streamline things:

  • Git can be set up to use a keyring to store your GitHub personal access token. Search online for the details.

  • You can use the keyring app to store the PyPI password for twine. See the online twine documentation for details.

Prior to release#

Add/drop Python versions#

When adding or dropping Python versions, three files need to be edited:

  • .github/workflows/wheels.yml # for github cibuildwheel

  • tools/ci/cirrus_wheels.yml # for cibuildwheel aarch64/arm64 builds

  • pyproject.toml # for classifier and minimum version check.

Make these changes in an ordinary PR against main and backport if necessary. Add [wheel build] at the end of the title line of the commit summary so that wheel builds will be run to test the changes. We currently release wheels for new Python versions after the first Python rc once manylinux and cibuildwheel support it. For Python 3.11 we were able to release within a week of the rc1 announcement.

Backport pull requests#

Changes that have been marked for this release must be backported to the maintenance/2.1.x branch.

Update 2.1.0 milestones#

Look at the issues/prs with 2.1.0 milestones and either push them off to a later version, or maybe remove the milestone. You may need to add a milestone.

Make a release PR#

Four documents usually need to be updated or created for the release PR:

  • The changelog

  • The release notes

  • The .mailmap file

  • The pyproject.toml file

These changes should be made in an ordinary PR against the maintenance branch. The commit heading should contain a [wheel build] directive to test if the wheels build. Other small, miscellaneous fixes may be part of this PR. The commit message might be something like:

REL: Prepare for the NumPy 2.1.0 release [wheel build]

- Create 2.1.0-changelog.rst.
- Update 2.1.0-notes.rst.
- Update .mailmap.
- Update pyproject.toml

Set the release version#

Check the pyproject.toml file and set the release version if needed:

$ gvim pyproject.toml

Check the pavement.py and doc/source/release.rst files#

Check that the pavement.py file points to the correct release notes. It should have been updated after the last release, but if not, fix it now. Also make sure that the notes have an entry in the release.rst file:

$ gvim pavement.py doc/source/release.rst

Generate the changelog#

The changelog is generated using the changelog tool:

$ spin changelog $GITHUB v2.0.0..maintenance/2.1.x > doc/changelog/2.1.0-changelog.rst

where GITHUB contains your GitHub access token. The text will need to be checked for non-standard contributor names and dependabot entries removed. It is also a good idea to remove any links that may be present in the PR titles as they don’t translate well to markdown, replace them with monospaced text. The non-standard contributor names should be fixed by updating the .mailmap file, which is a lot of work. It is best to make several trial runs before reaching this point and ping the malefactors using a GitHub issue to get the needed information.

Finish the release notes#

If there are any release notes snippets in doc/release/upcoming_changes/, run spin notes, which will incorporate the snippets into the doc/source/release/notes-towncrier.rst file and delete the snippets:

$ spin notes
$ gvim doc/source/release/notes-towncrier.rst doc/source/release/2.1.0-notes.rst

Once the notes-towncrier contents has been incorporated into release note the .. include:: notes-towncrier.rst directive can be removed. The notes will always need some fixups, the introduction will need to be written, and significant changes should be called out. For patch releases the changelog text may also be appended, but not for the initial release as it is too long. Check previous release notes to see how this is done.

Release walkthrough#

Note that in the code snippets below, upstream refers to the root repository on GitHub and origin to its fork in your personal GitHub repositories. You may need to make adjustments if you have not forked the repository but simply cloned it locally. You can also edit .git/config and add upstream if it isn’t already present.

1. Prepare the release commit#

Checkout the branch for the release, make sure it is up to date, and clean the repository:

$ git checkout maintenance/2.1.x
$ git pull upstream maintenance/2.1.x
$ git submodule update
$ git clean -xdfq

Sanity check:

$ python3 -m spin test -m full

Tag the release and push the tag. This requires write permission for the numpy repository:

$ git tag -a -s v2.1.0 -m"NumPy 2.1.0 release"
$ git push upstream v2.1.0

If you need to delete the tag due to error:

$ git tag -d v2.1.0
$ git push --delete upstream v2.1.0

2. Build wheels#

Tagging the build at the beginning of this process will trigger a wheel build via cibuildwheel and upload wheels and an sdist to the staging repo. The CI run on github actions (for all x86-based and macOS arm64 wheels) takes about 1 1/4 hours. The CI runs on cirrus (for aarch64 and M1) take less time. You can check for uploaded files at the staging repository, but note that it is not closely synched with what you see of the running jobs.

If you wish to manually trigger a wheel build, you can do so:

  • On github actions -> Wheel builder there is a “Run workflow” button, click on it and choose the tag to build

  • On Cirrus we don’t currently have an easy way to manually trigger builds and uploads.

If a wheel build fails for unrelated reasons, you can rerun it individually:

  • On github actions select Wheel builder click on the commit that contains the build you want to rerun. On the left there is a list of wheel builds, select the one you want to rerun and on the resulting page hit the counterclockwise arrows button.

  • On cirrus, log into cirrusci, look for the v2.1.0 tag and rerun the failed jobs.

3. Download wheels#

When the wheels have all been successfully built and staged, download them from the Anaconda staging directory using the tools/download-wheels.py script:

$ cd ../numpy
$ mkdir -p release/installers
$ python3 tools/download-wheels.py 2.1.0

4. Generate the README files#

This needs to be done after all installers are downloaded, but before the pavement file is updated for continued development:

$ paver write_release

5. Upload to PyPI#

Upload to PyPI using twine. A recent version of twine of is needed after recent PyPI changes, version 3.4.1 was used here:

$ cd ../numpy
$ twine upload release/installers/*.whl
$ twine upload release/installers/*.gz  # Upload last.

If one of the commands breaks in the middle, you may need to selectively upload the remaining files because PyPI does not allow the same file to be uploaded twice. The source file should be uploaded last to avoid synchronization problems that might occur if pip users access the files while this is in process, causing pip to build from source rather than downloading a binary wheel. PyPI only allows a single source distribution, here we have chosen the zip archive.

6. Upload files to GitHub#

Go to numpy/numpy, there should be a v2.1.0 tag, click on it and hit the edit button for that tag and update the title to ‘v2.1.0 (<date>). There are two ways to add files, using an editable text window and as binary uploads. Start by editing the release/README.md that is translated from the rst version using pandoc. Things that will need fixing: PR lines from the changelog, if included, are wrapped and need unwrapping, links should be changed to monospaced text. Then copy the contents to the clipboard and paste them into the text window. It may take several tries to get it look right. Then

  • Upload release/installers/numpy-2.1.0.tar.gz as a binary file.

  • Upload release/README.rst as a binary file.

  • Upload doc/changelog/2.1.0-changelog.rst as a binary file.

  • Check the pre-release button if this is a pre-releases.

  • Hit the {Publish,Update} release button at the bottom.

7. Upload documents to numpy.org (skip for prereleases)#

Note

You will need a GitHub personal access token to push the update.

This step is only needed for final releases and can be skipped for pre-releases and most patch releases. make merge-doc clones the numpy/doc repo into doc/build/merge and updates it with the new documentation:

$ git clean -xdfq
$ git co v2.1.0
$ rm -rf doc/build  # want version to be current
$ python -m spin docs merge-doc --build
$ pushd doc/build/merge

If the release series is a new one, you will need to add a new section to the doc/build/merge/index.html front page just after the “insert here” comment:

$ gvim index.html +/'insert here'

Further, update the version-switcher json file to add the new release and update the version marked (stable) and preferred:

$ gvim _static/versions.json

Then run update.py to update the version in _static:

$ python3 update.py

You can “test run” the new documentation in a browser to make sure the links work, although the version dropdown will not change, it pulls its information from numpy.org:

$ firefox index.html  # or google-chrome, etc.

Update the stable link and update:

$ ln -sfn 2.1 stable
$ ls -l  # check the link

Once everything seems satisfactory, update, commit and upload the changes:

$ git commit -a -m"Add documentation for v2.1.0"
$ git push [email protected]:numpy/doc
$ popd

8. Reset the maintenance branch into a development state (skip for prereleases)#

Create release notes for next release and edit them to set the version. These notes will be a skeleton and have little content:

$ git checkout -b begin-2.1.1 maintenance/2.1.x
$ cp doc/source/release/template.rst doc/source/release/2.1.1-notes.rst
$ gvim doc/source/release/2.1.1-notes.rst
$ git add doc/source/release/2.1.1-notes.rst

Add new release notes to the documentation release list and update the RELEASE_NOTES variable in pavement.py:

$ gvim doc/source/release.rst pavement.py

Update the version in pyproject.toml:

$ gvim pyproject.toml

Commit the result:

$ git commit -a -m"MAINT: Prepare 2.1.x for further development"
$ git push origin HEAD

Go to GitHub and make a PR. It should be merged quickly.

9. Announce the release on numpy.org (skip for prereleases)#

This assumes that you have forked numpy/numpy.org:

$ cd ../numpy.org
$ git checkout main
$ git pull upstream main
$ git checkout -b announce-numpy-2.1.0
$ gvim content/en/news.md

  • For all releases, go to the bottom of the page and add a one line link. Look to the previous links for example.

  • For the *.0 release in a cycle, add a new section at the top with a short description of the new features and point the news link to it.

commit and push:

$ git commit -a -m"announce the NumPy 2.1.0 release"
$ git push origin HEAD

Go to GitHub and make a PR.

10. Announce to mailing lists#

The release should be announced on the numpy-discussion, scipy-devel, and python-announce-list mailing lists. Look at previous announcements for the basic template. The contributor and PR lists are the same as generated for the release notes above. If you crosspost, make sure that python-announce-list is BCC so that replies will not be sent to that list.

11. Post-release update main (skip for prereleases)#

Checkout main and forward port the documentation changes. You may also want to update these notes if procedures have changed or improved:

$ git checkout -b post-2.1.0-release-update main
$ git checkout maintenance/2.1.x doc/source/release/2.1.0-notes.rst
$ git checkout maintenance/2.1.x doc/changelog/2.1.0-changelog.rst
$ git checkout maintenance/2.1.x .mailmap  # only if updated for release.
$ gvim doc/source/release.rst  # Add link to new notes
$ git status  # check status before commit
$ git commit -a -m"MAINT: Update main after 2.1.0 release."
$ git push origin HEAD

Go to GitHub and make a PR.

Branch walkthrough#

This guide contains a walkthrough of branching NumPy 1.21.x on Linux. The commands can be copied into the command line, but be sure to replace 1.21 and 1.22 by the correct versions. It is good practice to make .mailmap as current as possible before making the branch, that may take several weeks.

This should be read together with the general release guide.

Branching#

Make the branch#

This is only needed when starting a new maintenance branch. Because NumPy now depends on tags to determine the version, the start of a new development cycle in the main branch needs an annotated tag. That is done as follows:

$ git checkout main
$ git pull upstream main
$ git commit --allow-empty -m'REL: Begin NumPy 1.22.0 development'
$ git push upstream HEAD

If the push fails because new PRs have been merged, do:

$ git pull --rebase upstream

and repeat the push. Once the push succeeds, tag it:

$ git tag -a -s v1.22.0.dev0 -m'Begin NumPy 1.22.0 development'
$ git push upstream v1.22.0.dev0

then make the new branch and push it:

$ git branch maintenance/1.21.x HEAD^
$ git push upstream maintenance/1.21.x

Prepare the main branch for further development#

Make a PR branch to prepare main for further development:

$ git checkout -b 'prepare-main-for-1.22.0-development' v1.22.0.dev0

Delete the release note fragments:

$ git rm doc/release/upcoming_changes/[0-9]*.*.rst

Create the new release notes skeleton and add to index:

$ cp doc/source/release/template.rst doc/source/release/1.22.0-notes.rst
$ gvim doc/source/release/1.22.0-notes.rst  # put the correct version
$ git add doc/source/release/1.22.0-notes.rst
$ gvim doc/source/release.rst  # add new notes to notes index
$ git add doc/source/release.rst

Update pavement.py and update the RELEASE_NOTES variable to point to the new notes:

$ gvim pavement.py
$ git add pavement.py

Update cversions.txt to add current release. There should be no new hash to worry about at this early point, just add a comment following previous practice:

$ gvim numpy/_core/code_generators/cversions.txt
$ git add numpy/_core/code_generators/cversions.txt

Check your work, commit it, and push:

$ git status  # check work
$ git commit -m'REL: Prepare main for NumPy 1.22.0 development'
$ git push origin HEAD

Now make a pull request.