towncrier-fragment-check
A pre-commit hook and CLI that fails when a branch does
not add a towncrier changelog fragment. It
wraps towncrier check and fills the gaps around it.
What it adds to towncrier check
- Monorepos. Check several towncrier projects in one run with
--project, passing when any one of them has a fragment (--require any) or only when they all do (--require all). - Subdirectories.
towncrier checkresolves git's repository-relative paths against the working directory, so it never matches when run insidepackages/api/. This tool always runs it from the git toplevel. - Base branch. Resolved from the flag, the environment, or
origin/main, whichever git can find first. GitHub pull requests need no configuration. - Empty fragments. A blank fragment file satisfies
towncrier checkand yields a blank release note. It fails here unless you pass--allow-empty. - New branches.
--skip-new-branchpasses a branch's first push, when the pull request number that fragment names often embed does not exist yet.
Installation
default_install_hook_types: [pre-commit, pre-push]
repos:
- repo: https://github.com/ChartinoLabs/towncrier-fragment-check
rev: v0.1.0
hooks:
- id: towncrier-fragment-check
stages: [pre-push]
Then run pre-commit install.
The check describes a whole branch, not one commit, so pre-push is the
recommended stage: it asks once, when the branch becomes visible to reviewers.
To run at the pre-commit stage instead, set stages: [pre-commit] and pass
args: [--staged] so fragments staged in the current commit count.
Monorepos
Each independently released package in a monorepo usually has its own towncrier
configuration, fragment directory, and changelog. Name each one with
--project DIR, or --project DIR:CONFIG when the configuration is not in
that directory's pyproject.toml or towncrier.toml:
- id: towncrier-fragment-check
stages: [pre-push]
args:
- --project
- packages/api
- --project
- apps/web:apps/web/towncrier.toml
By default a fragment in any one project passes, which suits a pull request that
changes only one package. Add --require all when every project must carry its
own.
Continuous integration
On a GitHub pull request the base branch comes from GITHUB_BASE_REF. Check out
the full history so the diff is available:
jobs:
check-changelog-fragment:
if: github.event_name == 'pull_request'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
with:
fetch-depth: 0
- run: uvx towncrier-fragment-check==0.1.0 --project packages/api --project apps/web
The package is on PyPI, so
pipx run and pip install work too. If pre-commit already runs in CI, reuse
the configured hook with
pre-commit run --hook-stage pre-push towncrier-fragment-check --all-files.
Options
| Option | Description |
|---|---|
--project DIR[:CONFIG] |
Towncrier project to check, relative to the git toplevel. Repeat once per project. Defaults to the repository root. |
--require {any,all} |
Pass rule across projects. Default any. |
--compare-with BRANCH |
Base ref to diff against. |
--staged |
Include staged files, for the pre-commit stage. |
--allow-empty |
Do not fail on empty or whitespace-only fragments. |
--skip-new-branch |
Exit 0 when PRE_COMMIT_FROM_REF is all zeros. |
--verbose, -v |
Always print towncrier's full output. |
--version |
Print the version and exit. |
Base branch resolution
The first candidate git can resolve wins:
--compare-withTOWNCRIER_COMPARE_WITHGITHUB_BASE_REF, prefixed withorigin/when it contains no/origin/mainorigin/master- towncrier's own default
Exit codes
| Code | Meaning |
|---|---|
0 |
Passed. |
1 |
No fragment, an empty fragment, or no resolvable base ref. |
2 |
Usage error. |
Development
uv sync --group dev
uv run pre-commit install
uv run pytest
License
Apache-2.0. See LICENSE.
Metadata
Release files for towncrier-fragment-check 0.1.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 | Provenance | |
|---|---|---|---|---|
| towncrier_fragment_check-0.1.0.tar.gz | 81.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| towncrier_fragment_check-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.4 kB
Release files / towncrier_fragment_check-0.1.0.tar.gz
| Download URL | towncrier_fragment_check-0.1.0.tar.gz |
|---|---|
| Size | 81.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d0f4d88ce1352d942a8d9e08863b9d5f5e9eb144d3a0e81f29ef2869bb759157
|
|
BLAKE2b-256 checksum How to use checksums |
c60f77644521fd5c702225c31b437e2511c9707192f34443afb29979ba64f031
|
| 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 Sep 2, 2026.
Transparency logRelease files / towncrier_fragment_check-0.1.0-py3-none-any.whl
| Download URL | towncrier_fragment_check-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
875660654d7e548d4a42fe4aa276e54376824f6435197df88f073c4b82f8894c
|
|
BLAKE2b-256 checksum How to use checksums |
559fb067fe0092c399a31d42df85cead18fe7863e2cb0670478424913047c48b
|
| 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 Sep 2, 2026.
Transparency logSecurity for towncrier-fragment-check 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for towncrier_fragment_check-0.1.0.tar.gz
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 Sep 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.