Release PyGMT v0.19.0

[seisman]

Release: v0.19.0
Scheduled Date: 2026/06/XX
Pull request due date: 2026/06/XX
DOI: 10.5281/zenodo.XXXXXXX
Announcement draft: https://hackmd.io/@pygmt/xxxxxxxx

Priority PRs/issues to complete prior to release

• Implement Figure.pygmtlogo for the PyGMT logo #4616
  • Figure.pygmtlogo: Improved positioning of horizontal wordmark for circular PyGMT logo #4627
  • POC: Add PyGMT logo to README & docs #3845
  • POC + WIP: Figure.pygmtlogo: Implement the hexagonal logo #4631
  • Figure.pygmtlogo: Improved positioning of vertical wordmark for circular PyGMT logo #4637
• POC: Figure.paragraph: What you see is what you type for spaces and tabs #4605

Before release:

• Check SPEC 0 to see if we need to bump the minimum supported versions of GMT, Python and core package dependencies (NumPy, pandas, xarray)
• Review the "PyGMT Team" page @seisman
• README looks good on TestPyPI. Visit TestPyPI, click the latest pre-release, and check the homepage.
• Review new parameter names added/changed for clarity and consistency across the API
• Check to ensure that:
  • Deprecated workarounds/codes/tests are removed. Run grep -r "# TODO" --include="*.py" . to find all potential TODOs.
  • All tests pass in the "GMT Legacy Tests" workflow
  • All tests pass in the "GMT Dev Tests" workflow
  • All tests pass in the "Doctests" workflow
  • All links work in the "Check Links" workflow
• Update warnings in pygmt/_show_versions.py as well as notes in Not working transparency regarding GMT-Ghostscript incompatibility
• Reserve a DOI on Zenodo by clicking on "New Version"
• Finish up the "Changelog entry for v0.x.x" Pull Request (Use the previous changelog PR as a reference)
• Run make codespell to check common misspellings. If there are any, either fix them or add them to ignore-words-list in pyproject.toml
• Draft the announcement on https://hackmd.io/@pygmt

Release:

• At the PyGMT release page on GitHub:
  • Edit the draft release notes with the finalized changelog
  • Set the tag version and release title to vX.Y.Z
  • Make a release by clicking the 'Publish Release' button, this will automatically create a tag too
• Verify that all workflows triggered by the release pass
  • The latest version is correct on PyPI
  • The latest version is correct on https://www.pygmt.org/latest/
  • The release page has five assets, including baseline-images.zip, pygmt-docs.zip and pygmt-docs.pdf
• Download pygmt-X.Y.Z.zip (rename to pygmt-vX.Y.Z.zip) and baseline-images.zip from the release page, and upload the two zip files to https://zenodo.org/deposit, ensure that they are filed under the correct reserved DOI

After release:

• Update conda-forge pygmt-feedstock (Done automatically by conda-forge's bot. If you don't want to wait, open a new issue in the conda-forge/pygmt-feedstock repository with the title @conda-forge-admin, please update version. This will trigger the bot immediately. Remember to pin GMT, Python and SPEC0 versions)
• Bump PyGMT version on https://github.com/GenericMappingTools/try-gmt (after conda-forge update)
• Announce the release on:
  • GMT forum (do this announcement first! Requires moderator status)
  • ResearchGate (after forum announcement; download the ZIP file of the new release from Zenodo and add it as research item via the code category, be sure to include the corresponding new Zenodo DOI)
• Update release checklist template with any additional bullet points that may have arisen during the release

---

• Party 🎉 (don't tick before all other checkboxes are ticked!)