Read the freaking changelog is a tool to manage changelogs and versioning.
As the name implies, rtfc helps you produce clear, well-structured changelogs, leaving your users no excuse for being surprised by what changed between releases.
rtfc is heavily inspired by the great Towncrier project.
Installation
From PyPI:
pip install rtfc
Usage
Configure rtfc in the [tool.rtfc] table of your pyproject.toml (or in an rtfc.toml file), and add the insert marker to your changelog document:
[tool.rtfc]
changelog = "docs/source/changelog.rst"
Changelog
=========
.. rtfc-insert
Changelog entries are individual files created along the changes of a pull request, avoiding the merge conflicts a shared changelog file causes:
$ rtfc new --section bugfix --meta gh_issue=123 --content "Fix a bug."
Created changelog/d0592011.bugfix.rtfc
Each entry holds a TOML frontmatter and the change description, written in the documentation format of your project:
+++
date = 2026-08-06
nonce = "d0592011"
section = "bugfix"
[metadata]
gh_issue = 123
+++
Fix a bug.
Validate the configuration and the entries, typically in CI:
$ rtfc check
OK: 1 valid entries
On release, combine the entries into the changelog. The release notes are inserted after the marker, and the entry files are deleted:
$ rtfc build --version 1.2.0
Updated docs/source/changelog.rst
A sphinx extension is also provided, rendering the not-yet-released entries when building your documentation.
Metadata
Release files for rtfc 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rtfc-0.2.0.tar.gz | 124.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rtfc-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 156.4 kB
Release files / rtfc-0.2.0.tar.gz
| Download URL | rtfc-0.2.0.tar.gz |
|---|---|
| Size | 124.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf85f67407a4eb1d787e06071de1a0eaa9a808cff693b4a33f7f46f1875751cb
|
|
BLAKE2b-256 checksum How to use checksums |
7c1871a10b0486242c2cd2a9782e0837d5c2f6df47e72933c6b5514092dc91be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.
Transparency logRelease files / rtfc-0.2.0-py3-none-any.whl
| Download URL | rtfc-0.2.0-py3-none-any.whl |
|---|---|
| Size | 32.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3fe61c9b3df4a5f37274f56f9204a04404a4e70c808f938f365752778a813a9d
|
|
BLAKE2b-256 checksum How to use checksums |
b6494f59913ed192cf4f580a3f75cbc09b04921d32663636267b34f53f9db055
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.
Transparency log