Skip to content

#717 Release 25.8.0#718

Merged
adiroiban merged 14 commits intotrunkfrom
717-release-25.8.0
Aug 30, 2025
Merged

#717 Release 25.8.0#718
adiroiban merged 14 commits intotrunkfrom
717-release-25.8.0

Conversation

@adiroiban
Copy link
Member

@adiroiban adiroiban commented Aug 15, 2025

Description

Fixes #717

THis is the PR for a new release

Release process documented at https://towncrier.readthedocs.io/en/stable/release.html

@adiroiban adiroiban requested a review from a team as a code owner August 15, 2025 09:25
@adiroiban
Copy link
Member Author

adiroiban commented Aug 15, 2025

Not the cleanest release ... pre-commit was not invited ...

I have to update the release github action

Relese candidate available for testing

This was referenced Aug 15, 2025
@webknjaz
Copy link
Contributor

FTR, here's a compat tracking issue in my Sphinx extension: sphinx-contrib/sphinxcontrib-towncrier#121. So far, only one test is failing but given that I'm reaching into private APIs in there, it shouldn't be a blocker here, upstream.

@webknjaz
Copy link
Contributor

NEWS.rst Outdated
- When used with an `pyproject.toml` file, when no explicit values are
defined for [tool.towncrier.name|package] they will now fallback to
the value of [project.name]. (`#687 <https://github.com/twisted/towncrier/issues/687>`_)
- More simple configuration for Keep a Changelog style changelogs (`#691 <https://github.com/twisted/towncrier/issues/691>`_)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This entry isn't very clear from the PoV of an end-user. Reading it in the change log, I don't understand what the effect is for me.

Comment on lines +40 to +42
- When no sections are present,
the default Markdown template now renders the category headers as H2.
In previous versions it was rendered as H3. (`#663 <https://github.com/twisted/towncrier/issues/663>`_)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this entry be under removals it's a feature / behavior change if you ask me.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can have a better name for Deprecations and Removals ... basically.
under Deprecations and Removals we have any "breaking changes"

We can look to update the template and use "Breaking changes"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@adiroiban yeah, I should probably propose updating the default templates. Over at @aio-libs and in other projects, I ended up having more accurate categories like contrib/packaging/downstream: https://yarl.aio-libs.org/en/latest/changes/#id100 / https://yarl.aio-libs.org/en/latest/contributing/guidelines/#alright-so-how-to-add-a-news-fragment / https://github.com/aio-libs/yarl/blob/b8d06ec9a7d95ac11437afd5e467c2c2bb1704d2/towncrier.toml#L18-L68.

Though, I wouldn't consider this all a part of the release PR. It's probably best to postpone until post-release.

Misc
----

- `#667 <https://github.com/twisted/towncrier/issues/667>`_, `#669 <https://github.com/twisted/towncrier/issues/669>`_, `#679 <https://github.com/twisted/towncrier/issues/679>`_, `#680 <https://github.com/twisted/towncrier/issues/680>`_, `#682 <https://github.com/twisted/towncrier/issues/682>`_, `#701 <https://github.com/twisted/towncrier/issues/701>`_, `#702 <https://github.com/twisted/towncrier/issues/702>`_, `#713 <https://github.com/twisted/towncrier/issues/713>`_
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this have to be a single bullet point?

Suggested change
- `#667 <https://github.com/twisted/towncrier/issues/667>`_, `#669 <https://github.com/twisted/towncrier/issues/669>`_, `#679 <https://github.com/twisted/towncrier/issues/679>`_, `#680 <https://github.com/twisted/towncrier/issues/680>`_, `#682 <https://github.com/twisted/towncrier/issues/682>`_, `#701 <https://github.com/twisted/towncrier/issues/701>`_, `#702 <https://github.com/twisted/towncrier/issues/702>`_, `#713 <https://github.com/twisted/towncrier/issues/713>`_
`#667 <https://github.com/twisted/towncrier/issues/667>`_, `#669 <https://github.com/twisted/towncrier/issues/669>`_, `#679 <https://github.com/twisted/towncrier/issues/679>`_, `#680 <https://github.com/twisted/towncrier/issues/680>`_, `#682 <https://github.com/twisted/towncrier/issues/682>`_, `#701 <https://github.com/twisted/towncrier/issues/701>`_, `#702 <https://github.com/twisted/towncrier/issues/702>`_, `#713 <https://github.com/twisted/towncrier/issues/713>`_.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is how it's implemented now in the template and is how we did it in the past


the ".misc" items might not have a description

Now... if you ask me, I would say that we should not list these items at all in the release notes


But this is a discussion for a separate issue/PR

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. This is separate. Though, I feel like misc items should be rendered with content, just like the others. If something isn't necessary in the change log, it should just not have a note to begin with.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the .misc notes. ... but I agree they should not be rendered.

They are an explicit confirmation that the changes are not public.

It makes it easier to raise an errror in the case you accidentally forget to update the release notes for a public change.


We can look into this as part of updating the template that we user towncrier

We don't have to change the default template , towncrier can have a custom template ... but I think that it makese sense for towncrier itself to use the default template

I am happy to update the default template... but in a separate issue

@webknjaz
Copy link
Contributor

webknjaz commented Aug 18, 2025

FTR, here's a compat tracking issue in my Sphinx extension: sphinx-contrib/sphinxcontrib-towncrier#121. So far, only one test is failing but given that I'm reaching into private APIs in there, it shouldn't be a blocker here, upstream.

UPD: it looks like there's no need for any compat code in there, just a test adjustment. I've added 25.8.0rc2 to the CI matrix and it's green: sphinx-contrib/sphinxcontrib-towncrier@ab800bc / https://github.com/sphinx-contrib/sphinxcontrib-towncrier/actions/runs/17045398297.

Co-authored-by: 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) <sviat@redhat.com>
@adiroiban
Copy link
Member Author

adiroiban commented Aug 20, 2025

Thanks for the review. Much appreciated.

I have applied your suggestions.

The result is at

https://towncrier--718.org.readthedocs.build/en/718/release-notes.html

I guess that we are ready for a new release


I am happy to change the template of our release notes... but this needs a separate issue.
I would also like to have both RST and MD versions generated at the same time... it should make it easier to copy/paste to GitHub Releases

I am happy to rename Deprecations and Removals to Deprecations, Removals, and Backward Incompatiblity

@webknjaz
Copy link
Contributor

I am happy to change the template of our release notes... but this needs a separate issue. I would also like to have both RST and MD versions generated at the same time... it should make it easier to copy/paste to GitHub Releases

I am happy to rename Deprecations and Removals to Deprecations, Removals, and Backward Incompatiblity

Yeah, I have workflows that use pandoc to produce markdown and show it in regular CI runs like https://github.com/cherrypy/cheroot/actions/runs/16225594939/attempts/1#summary-45816734060 + GH Releases/Discussions cherrypy/cheroot#694, with --draft written into a temporary file and some light post-processing.

However, I feel like it's so much easier to just switch over to Markdown with MyST-Parser.

This is something to consider after releasing, though.

@webknjaz
Copy link
Contributor

@adiroiban I think this is ready for a final release, FWIW.

adiroiban and others added 2 commits August 30, 2025 12:29
Co-authored-by: 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко) <sviat@redhat.com>
@adiroiban
Copy link
Member Author

adiroiban commented Aug 30, 2025

Many thanks for the review and great feedback. Much appreciated.

I have trigger the release at https://github.com/twisted/towncrier/actions/runs/17343314258

PyPI at https://pypi.org/project/Twisted/25.5.0/

As mentions, I am happy to change the default template...but this needs to be discussed in a separate issue.
For me the default template is not a big deal... I set it more 7 years ago... and since then I never had to worry about it.

@adiroiban adiroiban merged commit c8a79cf into trunk Aug 30, 2025
16 checks passed
@adiroiban adiroiban deleted the 717-release-25.8.0 branch August 30, 2025 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Time for a new release?

2 participants