Release v1.8.1

[leouieda]

Bug fix release with some repository maintenance and 2 bug fixes.

Zenodo DOI: 10.5281/zenodo.10680982

Target date: 2024/02/19

Draft a Zenodo archive (to be done by a manager on Zenodo)

• [x] Go to the Zenodo entry for this project (find the link to the latest Zenodo release on the README.md file)
• [x] Create a "New version" of it.
• [x] Delete all existing files
• [x] Copy the reserved DOI to this issue
• [x] Update release date
• [x] Update version number (make sure there is a leading v, like v1.5.7)
• [x] Update version number in Title (use a leading v as well)
• [x] Add as authors any new contributors who have added themselves to AUTHORS.md in the same order
• [x] Ensure that the first author is "Fatiando a Terra Project" and others are listed alphabetically by last name
• [x] Save the release draft

Update the changelog

• [x] Generate a list of commits between the last release tag and now: git log HEAD...v1.2.3 > changes.rst
• [x] Edit the list to remove any trivial changes (updates by the bot, CI updates, etc).
• [x] Organize the list into categories (breaking changes, deprecations, bug fixes, new features, maintenance, documentation).
• [x] Add a list of people who contributed to the release:

  export last_release="v1.2.3"
  git shortlog HEAD...$last_release -sne > contributors
  git log HEAD...$last_release | grep "Co-authored-by" | sed 's/Co-authored-by://' | sed 's/^[[:space:]]*/ /' | sort | uniq -c | sort -nr | sed 's/^ //' >> contributors
  sort -rn contributors

• [x] Add the release date and Zenodo DOI badge to the top
• [x] Replace the PR numbers with links: sed --in-place "s,#\([0-9]\+\),\`#\1 <https://github.com/fatiando/PROJECT/pull/\1>\`__,g" changes.rst
• [x] Check that you changed the PROJECT placeholder when running the last command.
• [x] Copy the changes to doc/changes.rst
• [x] Make a Markdown copy of the changelog: pandoc -s changes.rst -o changes.md --wrap=none
• [x] Add a link to the new release version documentation in README.rst and doc/versions.rst (if the file exists).
• [x] Build and serve the docs locally with make -C doc all serve to check if the changelog looks well
• [x] Open a PR to update the changelog
• [x] Merge the PR

Make a release

After the changelog PR is merged:

• [x] Draft a new release on GitHub
• [x] The tag and release name should be a version number (following Semantic Versioning) with a leading v (v1.5.7)
• [x] Fill the release description with a Markdown version of the latest changelog entry (including the DOI badge)
• [x] Publish the release

Publish to Zenodo

• [x] Upload the zip archive from the GitHub release to Zenodo
• [x] Double check all information (date, authors, version)
• [x] Publish the new version on Zenodo

Conda-forge package

A PR should be opened automatically on the project feedstock repository.

• [x] Add/remove/update any dependencies that have changed in meta.yaml
• [x] If dropping/adding support for Python/numpy versions, make sure the correct version restrictions are applied in meta.yaml
• [x] Merge the PR

[leouieda]

@jni we'd love to list you as an author on the Zenodo archive. If you'd like that, please add yourself to the AUTHORS.md file in the repository. No rush, we can wait to push the release.

[jni]

Thanks for the invitation! 🙏 I have done this in #396.