0.9rc1

[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.9rc1 later today. Any reason to delay?

[choldgraf]

It would be nice to get the color variables PR in the next release, but I think it's totally fine to get a pre release out now so that others can test

[jarrodmillman]

I was just looking at that PR. Is there more that needs to be done (other than resolving the merge conflicts)? It looked to me like it was ready to merge other than the question regarding whether to put all the CSS variables in one location. If so, would it make sense to merge the PR and create an issue to figure out the directory thing later.

[choldgraf]

I've also just finished off the master -> main work that you provided guidance on @jarrodmillman - so I think we are nearly ready to release?

[jarrodmillman]

I will make the 0.9rc1 release tomorrow morning. Thanks!

[jarrodmillman]

• https://github.com/pydata/pydata-sphinx-theme/releases/tag/v0.9.0rc1
• https://pypi.org/project/pydata-sphinx-theme/0.9.0rc1/