Skip to content

Build the changelog from news/ fragments with towncrier - #434

Open
RonnyPfannschmidt wants to merge 1 commit into
mainfrom
claude/project-thread-p4bz94
Open

RonnyPfannschmidt wants to merge 1 commit into
mainfrom
claude/project-thread-p4bz94

Conversation

@RonnyPfannschmidt

Copy link
Copy Markdown
Member

Requested by Ronny · project thread

🤖 Written by Claude Opus 5.5 via Claude Code for the execnet maintainers; I prompted it, it did the work, I read it.

Before: the "Changelog entry" check requires a news/ fragment, but nothing builds them and RELEASING.rst says to edit CHANGELOG.rst by hand. #429 (from #431) ended up listed in both places, and the #430 fragment would never reach a release.

After: towncrier build turns the news/ fragments into the release section of CHANGELOG.rst, and the fragments are the only place to record changes.

How: add [tool.towncrier] to pyproject.toml (keeping the existing #NNN <url> link style), add the .. towncrier release notes start marker to CHANGELOG.rst, move the pending #380 entry into news/380.feature.rst, drop the hand-written #429 entry (its fragment already exists), and document the build step in RELEASING.rst. uvx towncrier build --draft --version 2.2.0 renders #380 and #430 under Features and #429 under Bugfixes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MiQ7iUinBNk9vMp1sGqZv1


Generated by Claude Code

The changelog check already requires a news/ fragment per PR, but nothing
built them: CHANGELOG.rst was edited by hand, so #429 ended up listed in
both places. Configure towncrier, move the pending #380 entry into a
fragment, drop the duplicate #429 entry and document the build step in
RELEASING.rst.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MiQ7iUinBNk9vMp1sGqZv1

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants