Release 0.16.1

[trallard]

Double check for quality-control

• There are no open issues with a impact: block-release label
• Check wether the localization files are up-to-date, or open a PR to update them if needed. i18n - Update localisation files #2072

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
  • The publish github action job has completed successfully in the actions tab.
  • The PyPI version is updated
• Hide the previous patch version build in the RDT interface if needed.
• Celebrate, you're done! 🎉

[dbitouze]

Shouldn't it be 0.16.1 instead of 0.1.6.1?

[trallard]

Yes you are right, I accidentally added a . in the issue title.

[trallard]

🏷️ 0.16.1rc0 is out now - will leave this discussion open should we encounter any issues and will be cutting a full release after at least a week.

[trallard]

It has been a week since the release candidate was published and we have not gotten any major issue reports so I decided to cut the 0.16.1 release 🚀 🏷️