Path to 0.19.0

[Yann-P]

Small fixes:

• UI fix at intermediate width [css] De-jumble header items at intermediate widths :) #1784
• Pipeline always failing on the main branch Fix code coverage workflow #2393
• Unwanted vertical scrollbar in mathjax container Fix vertical scrollbar in math container #2404
• Text-only builds failing Fix gettext builder #2403

Initially planned but unrealistic: #2187.

Current diff from latest release: v0.18.0...main

[Yann-P]

Two suggestions for this release in the light of the recent github controversies... might be useful later, who knows

#2068

#2215

[maximlt]

#2187 looks like a big change and so whenever it is ready it'd be nice for downstream users to have some time to try it out and provide feedback, before it is released.

[Yann-P]

I agree, it is such an important change we will need a few RCs before releasing this.

It sounds unrealistic for 0.19.0 anyway, as we have not heard from the author. This is far from trivial to carry on the work of this PR

[Yann-P]

Release: https://github.com/pydata/pydata-sphinx-theme/releases/tag/v0.19.0rc0

[Carreau]

Step for release.

Double check for quality-control

• There are no open issues with a impact: block-release label
• Check whether the localization files are up-to-date, or open a PR to update them if needed.
  • only minor line number changes so far.

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
• If it's a pre-release, activate it in RDT interface (Add version).
• Hide the previous patch version build in the RDT interface if needed.
• Open a new PR to bump the version to the next dev target (e.g. 0.2.1.dev0) in __init__.py
• Celebrate, you're done!

[Yann-P]

It is up on PyPI, Condaforge and RTD so closing.

Thanks @Carreau for handling this release!