How to Make a Release

A core developer should use the following steps to create a release X.Y.Z of pynwb.

Note

Since the pynwb wheels do not include compiled code, they are considered pure and could be generated on any supported platform.

That said, considering the instructions below have been tested on a Linux system, they may have to be adapted to work on macOS or Windows.

Prerequisites

  • All CI tests are passing on GitHub Actions.

  • You have a GPG signing key.

  • Dependency versions in requirements.txt, requirements-dev.txt, requirements-opt.txt, requirements-doc.txt, and requirements-min.txt are up-to-date.

  • Legal information and copyright dates in Legal.txt, license.txt, README.rst, docs/source/conf.py, and any other files are up-to-date.

  • Package information in setup.py is up-to-date.

  • README.rst information is up-to-date.

  • The nwb-schema submodule is up-to-date. The version number should be checked manually in case syncing the git submodule does not work as expected.

  • Documentation reflects any new features and changes in PyNWB functionality.

  • Documentation builds locally.

  • Documentation builds on the ReadTheDocs project on the “dev” build.

  • Release notes have been prepared.

  • An appropriate new version number has been selected.

Documentation conventions

The commands reported below should be evaluated in the same terminal session.

Commands to evaluate starts with a dollar sign. For example:

$ echo "Hello"
Hello

means that echo "Hello" should be copied and evaluated in the terminal.

Publish release on PyPI: Step-by-step

  1. Make sure that all CI tests are passing on GitHub Actions.

  2. List all tags sorted by version.

$ git tag -l | sort -V
  1. Choose the next release version number and store it in a variable.

$ release=X.Y.Z

Warning

To ensure the packages are uploaded on PyPI, tags must match this regular expression: ^[0-9]+.[0-9]+.[0-9]+$.

  1. Download the latest sources.

$ cd /tmp && git clone --recurse-submodules git@github.com:NeurodataWithoutBorders/pynwb && cd pynwb
  1. Tag the release.

$ git tag --sign -m "pynwb ${release}" ${release} origin/dev

Warning

This step requires a GPG signing key.

  1. Publish the release tag.

$ git push origin ${release}

Important

This will trigger the “Deploy release” GitHub Actions workflow which will automatically upload the wheels and source distribution to both the PyNWB PyPI project page and a new GitHub release using the nwb-bot account.

  1. Check the status of the builds on GitHub Actions.

  2. Once the builds are completed, check that the distributions are available on PyNWB PyPI project page and that a new GitHub release was created.

  3. Copy the release notes from CHANGELOG.md to the newly created GitHub release.

  4. Create a clean testing environment to test the installation.

On bash/zsh:

$ python -m venv pynwb-${release}-install-test && \
  source pynwb-${release}-install-test/bin/activate

On other shells, see the Python instructions for creating a virtual environment.

  1. Test the installation:

$ pip install pynwb && \
  python -c "import pynwb; print(pynwb.__version__)"
  1. Cleanup

On bash/zsh:

$ deactivate && \
  rm -rf dist/* && \
  rm -rf pynwb-${release}-install-test

Publish release on conda-forge: Step-by-step

Warning

Publishing on conda requires you to have the corresponding package version uploaded on `PyPI`_. So you have to do the PyPI and Github release before you do the conda release.

Note

Conda-forge maintains a bot called “regro-cf-autotick-bot” that regularly monitors PyPI for new releases of packages that are also on conda-forge. When a new release is detected, usually within 24 hours of publishing on PyPI, the bot will create a Pull Request with the correct modifications to the version and sha256 values in meta.yaml. If the requirements in setup.py have been changed, then you need to modify the requirements/run section in meta.yaml manually to reflect these changes. Once tests pass, merge the PR, and a new release will be published on Anaconda cloud. This is the easiest way to update the package version on conda-forge.

In order to release a new version on conda-forge manually, follow the steps below:

  1. Store the release version string (this should match the PyPI version that you already published).

$ release=X.Y.Z
  1. Fork the pynwb-feedstock repository to your GitHub user account.

  2. Clone the forked feedstock to your local filesystem.

    Fill the YOURGITHUBUSER part.

    $ cd /tmp && git clone https://github.com/YOURGITHUBUSER/pynwb-feedstock.git
    
  3. Download the corresponding source for the release version.

$ cd /tmp && \
  wget https://github.com/NeurodataWithoutBorders/pynwb/releases/download/$release/pynwb-$release.tar.gz
  1. Create a new branch.

    $ cd pynwb-feedstock && \
      git checkout -b $release
    
  2. Modify meta.yaml.

    Update the version string and sha256.

    We have to modify the sha and the version string in the meta.yaml file.

    For linux flavors:

    $ sed -i "2s/.*/{% set version = \"$release\" %}/" recipe/meta.yaml
    $ sha=$(openssl sha256 /tmp/pynwb-$release.tar.gz | awk '{print $2}')
    $ sed -i "3s/.*/{$ set sha256 = \"$sha\" %}/" recipe/meta.yaml
    

    For macOS:

    $ sed -i -- "2s/.*/{% set version = \"$release\" %}/" recipe/meta.yaml
    $ sha=$(openssl sha256 /tmp/pynwb-$release.tar.gz | awk '{print $2}')
    $ sed -i -- "3s/.*/{$ set sha256 = \"$sha\" %}/" recipe/meta.yaml
    

If the requirements in setup.py have been changed, then modify the requirements/run list in the meta.yaml file to reflect these changes.

  1. Push the changes to your fork.

    $ git push origin $release
    
  2. Create a Pull Request.

    Create a pull request against the main feedstock repository. After the tests pass, merge the PR, and a new release will be published on Anaconda cloud.