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
4.3.0 release plan #9824
Comments
sounds good, thanks @tk0miya-san |
No concerns from my side. |
LGTM! |
Well, that didn't last long: a variation of #9833 should probably go into 4.x before release. |
I will ship a new version after #9833 will be merged. Maybe within 24 hours. |
Just released! Thank you for all your work! |
@tk0miya for your release steps, can you also add:
thanks! |
@jmckenna Could you explain (or give me a pointer) the advantage of the GitHub releases? TBH, I'd not like to increase tasks on releasing... |
It would be nice if GHA automatically generates a release on tagging :-) |
It's helpful if somebody posts a PR :-) |
@tk0miya if you click that button that I said earlier, a new tag is auto-generated for the release, and the archives are auto-generated for the release, all you have to do is paste the text: "Sphinx 4.3.0 release is now available, as a bug-fix release. Please see the changelog at https://www.sphinx-doc.org/en/master/changes.html Thank-you to the whole community." <--and the 130+ "watchers" for this repository are auto-magically notified. |
Please see PR #9842. https://github.com/actions/create-release is archived, so of the ones linked from there, this uses the one with the most stars: https://github.com/softprops/action-gh-release |
I merged #9842 now. Please wait for the next release. |
Hi maintainers,
About 2months has passed since the last stable release. Based on our release cycle, I'll ship a new package 4.3.0 in nearly days. Do you have any concerns?
Note: issues marked as 4.3.0:
https://github.com/sphinx-doc/sphinx/milestone/114
The text was updated successfully, but these errors were encountered: