-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release 0.15.3 #1797
Comments
Release candidate is out: https://github.com/pydata/pydata-sphinx-theme/releases/tag/v0.15.3rc0 Weds 08 May is the target for full release. Please comment below links to any issues that folks think ought to be release blockers / are small enough bugfixes that they wouldn't need a second round RC. Maintainers: if you agree with a user about any suggested blockers, please add the |
I'm noticing some buggy behavior with the current/latest PyData Theme docs site. Seems potentially related. When I go to https://pydata-sphinx-theme.readthedocs.io/en/latest/index.html, I expect to see "dev" in the version dropdown but it shows "0.15.3 (stable)" instead, and then if I click on 0.15.3, I get taken to a new page with a version warning banner at the top that says "This is documentation for an old version (0.15.2). Switch to stable version." But if I click the "Switch to stable version" button-link, I get the same version warning. |
thanks for reporting. We should definitely fix that before full release (hopefully it is a config error for our site related to the RC, not a general problem for all sites) |
I think it is indeed related to the fact that |
Any plans to push the RC to pypi for ease of testing? |
ha. yes, thanks for the nudge. It was supposed to happen automatically but I did the release in a hurry / didn't check, and then forgot. |
OK the RC has been on PyPI for ~8 days, so I plan to cut an official release today. I scanned the commits since the last RC and IMO they're all either not user-facing (test, maint, CI) or minor enough to make it OK to wrap into the release (with the possible exception of #1757) |
Could you elaborate how to test this RC via PyPI? |
|
release is blocked by #1818 |
@drammock I believe this is now unblocked. |
all done! thanks for unblocking @trallard |
Double check for quality-control
impact: block-release
labelPrepare the codebase for a new version
__version__
in__init__.py
.json
file with the new versiongit commit -m 'bump: 0.1.9 → 0.2.0'
git push upstream main
Make the release
v0.2.0
Choose a Tag:
dropdown, type in the release name (e.g.,v0.2.0
) and click "Create new tag"Target:
dropdown, pin it to the release commit that you've just pushed.publish
github action job has completed successfully in the actions tab.closes #1729
The text was updated successfully, but these errors were encountered: