0.9 release!

[jarrodmillman]

• Bump __version__ in __init__.py.
  • Use semantic versioning to decide whether it's a major, minor, or patch bump.
  • Before we have released 1.0, treat minor versions as breaking releases, and patch versions as feature / patch releases.
• Update our version switcher .json file with the new version
• Make a release commit: git commit -m 'RLS: v0.2.0'
• Push the RLS commit git push upstream master
• Make a 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.
  • Add release notes in the field below (if it's a minor/major version bump)
    If you wish, use github-activity to generate a changelog, eg github-activity pydata/pydata-sphinx-theme --since v0.2.2 --until v0.3.0.
  • Confirm that this github action job has completed successfully in the actions tab
  • Confirm that the PyPI version is updated
• Celebrate, you're done!

@choldgraf I plan to release 0.9 tomorrow afternoon. Any reason to delay?

[12rambau]

I see 2 major issues that will IMO break a lot of already existing documentations:

• Reconsider dark mode default behavior #684
• Support a logo for the dark theme #674

As the release of 0.9 will make the dark theme available for everyone maybe we should wait for these 2 to be solved first.
I'm going to work on them this WE It's pretty straight forward

[choldgraf]

little tweet thread about it is here: https://twitter.com/choldgraf/status/1534788736512311301