Skip to content

Release 0.16.0 #1948

Closed
Closed
@Carreau

Description

I think with the recent sphinx 8 fixes it woudl be good to make a new release potentially dropping older shinx. Here are the list of things to do for a new release.

Double check for quality-control

Prepare the codebase for a new version

  • Bump __version__ in __init__.py
  • Update our version switcher .json file with the new version
  • Make a release commit: git commit -m 'bump: 0.1.9 → 0.2.0'
  • Push the RLS commit git push upstream main
  • If a release candidate is needed, tick this box when we're now ready for a full release.

Make the release

  • Start a new GitHub release
    • Call the release the current version, e.g. v0.2.0
    • In the Choose a Tag: dropdown, type in the release name (e.g., v0.2.0) and click "Create new tag"
    • In the Target: dropdown, pin it to the release commit that you've just pushed.
    • Generate the automatic release notes, eventually manually specify the previous version (useful when several release candidate have been made)
  • Confirm that the release completed
  • Hide the previous patch version build in the RDT interface if needed.
  • Celebrate, you're done!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    kind: releaseItems related to PST releases

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions