-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
DOC: Build release notes during CircleCI step #14514
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
Conversation
b6d65e2
to
b3bc936
Compare
5e00f83
to
dc83da1
Compare
981ffda
to
85b230b
Compare
85814c3
to
0a2d097
Compare
OK, tested locally, sorry for the previous spam. The test script triggers, the release notes seem to render fine. |
For the moment, this requires te use for the development version of towncrier.
0a2d097
to
958a6b5
Compare
Rephrased that one slightly. Just noticed that towncrier has a small bug with the new single file option. It was supposed to ignore existing content (and default to old behaviour). Not a big issue, although I suppose we may have to adapt the pyproject.toml once that is fixed (if you scroll down the old content is still there at the end). |
Thanks @seberg. The first iteration of the final release note may need some editing by hand, but this will allow us to see the note as it evolves. |
For the moment, this requires te use for the development version
of towncrier.
I will check CI, there are likely smaller things that needs fixing in existing fragments, if not, I may just merge soon, so that the fragments are tested (at least for rst errors).