Skip to content

Release PyGMT v0.19.0 #4649

Closed
Closed

Description

@seisman

Release: v0.19.0
Scheduled Date: 2026/07/05
Pull request due date: 2026/07/05
DOI: 10.5281/zenodo.19398871
Announcement draft: https://hackmd.io/xgfUvmc4TMW-fOGMoi_IbQ

Priority PRs/issues to complete prior to release

Before release:

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
  • 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:


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

Activity

  1. pinned this issue on May 21, 2026
  2. added this to the 0.19.0 milestone on May 22, 2026
  3. seisman commented on Jul 8, 2026

    @seisman
    MemberAuthor

    @yvonnefroehlich I'm encountering internet connection issues accessing Zenodo. Could you please upload this version to Zenodo ?

  4. yvonnefroehlich commented on Jul 8, 2026

    @yvonnefroehlich
    Member

    @yvonnefroehlich I'm encountering internet connection issues accessing Zenodo. Could you please upload this version to Zenodo ?

    Sure, I looked at this. I expected to see an unpublished draft record (see example from my own uploads) with the reserved DOI, but I can only find the published record for v0.18.0:

    Image Image

    Maybe a draft record is only visible to the person who created it? Or I do not have enough permission (https://help.zenodo.org/docs/communities/about-communities/) as a Curator (you and @weiji14 are Owners)? Clicking "New upload" would lead to an upload, which is not listed as a version of the PyGMT upload. Clicking "New version" was already done to reserve the DOI and doing this again would generate a new DOI.

  5. weiji14 commented on Jul 9, 2026

    @weiji14
    Member

    Ok, I've done the Zenodo uploads. Have also added the paper DOI under 'Related Works' -> 'Is published in':

    Image

    @yvonnefroehlich, I've bumped your permissions from Curator to Manager. Not sure if it helps you to see draft uploads, can check next time.

  6. yvonnefroehlich commented on Jul 9, 2026

    @yvonnefroehlich
    Member

    Ok, I've done the Zenodo uploads. Have also added the paper DOI under 'Related Works' -> 'Is published in':

    @yvonnefroehlich, I've bumped your permissions from Curator to Manager. Not sure if it helps you to see draft uploads, can check next time.

    Great! Thanks 🙂.

  7. seisman commented on Jul 17, 2026

    @seisman
    MemberAuthor

    I'm still on a trip and have limited access to HackMD. For the announcement, I suggest we:

    • PyGMT paper section: Add a note acknowledging the typo in the PyGMT paper DOI.

    • Frame/Axis classes: These are new features that deserve a more thorough introduction. It would be helpful to include a side-by-side example comparing the legacy list syntax with the new class syntax, e.g.:

      Old syntax:

      frame=["xaf+lX", "yaf+lY", "+tTitle"]

      New syntax:

      frame=Frame(
          xaxis=Axis(annot=True, tick=True, label="X"),
          yaxis=Axis(annot=True, tick=True, label="Y"),
          title="Title"
      )

      and link to the frames tutorial at https://www.pygmt.org/v0.19.0/tutorials/basics/frames.html

  8. yvonnefroehlich commented on Jul 17, 2026

    @yvonnefroehlich
    Member

    I'm still on a trip and have limited access to HackMD. For the announcement, I suggest we:

    I should have time today to fill the table for the examples and include these ideas into the announcement. If people have time proofreading would be nice afterwards, and then I could post it later the day (evening or night).

  9. seisman commented on Jul 17, 2026

    @seisman
    MemberAuthor
    • PyGMT paper section: Add a note acknowledging the typo in the PyGMT paper DOI.

    I feel this is no longer necessary because the typo is only visible in the README file of the source code archive after @weiji14's fix in #4730, so it should have limited effect.

  10. yvonnefroehlich commented on Jul 17, 2026

    @yvonnefroehlich
    Member

    I'm still on a trip and have limited access to HackMD. For the announcement, I suggest we:

    I should have time today to fill the table for the examples and include these ideas into the announcement. If people have time proofreading would be nice afterwards, and then I could post it later the day (evening or night).

    I have filled the table to show the new and updated examples, added a separate subsection for the Axis and Frame parameter with the simple comparison example from Dongdong, included an image of the new PyGMT logo, and added a link to the JNs published along with the PyGMT paper.
    I realized that besides the examples we already mentioned, the choropleth gallery example and the basic tutorial for setting the map frame were updated to use the high-level method and new parameter classes. Thus, I changed it to ten instead of eight new and updated examples.

    I plan to post the announcement in the evening or night. So, @michaelgrund and @weiji14 if you have time, please have a look to see that everything looks good.

  11. yvonnefroehlich commented on Jul 17, 2026

    @yvonnefroehlich
    Member
  12. seisman commented on Jul 18, 2026

    @seisman
    MemberAuthor
  13. unpinned this issue on Jul 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    maintenanceBoring but important stuff for the core devs

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions