𝗰𝗼𝗺𝗺𝗶𝘁𝗶𝘇𝗲𝗻-𝚜𝚙𝚍𝚡-𝓬𝓱𝓪𝓷𝓰𝓮𝓵𝓸𝓰
A commitizen changelog format plugin with YAML frontmatter awareness —
designed for REUSE/SPDX-compliant changelogs. No more false version detection
from license headers like Apache-2.0.
Warning: This project is in early development.
Features
- SPDX-aware — strips
----delimited YAML frontmatter before parsing - Correct version detection — no false positives from
Apache-2.0style headers - Drop-in replacement — extends commitizen's built-in
Markdownformat - Zero extra config — just set
changelog_format = "spdx-markdown"
Why do I need this?
If you keep your changelog in docs/changelog.md instead of the project root,
placing it alongside your documentation lets readers of your published site who
might not directly browse the git repository stay informed about recent changes.
Documentation generators like Zensical, Docusaurus, and tools using Google's
Open Knowledge Format (OKF) require a YAML front matter for meta data.
When you apply a REUSE/SPDX license header with reuse annotate, the
header lands as a YAML comment inside the front matter, not as an HTML comment:
# SPDX-License-Identifier: Apache-2.0
The catch: commitizen's built-in Markdown format does not understand YAML
front matter. It reads Apache-2.0 as a version number, causing
cz bump --changelog to fail silently or produce wrong results.
This plugin strips the front matter before parsing, so your changelog stays compliant, doc-generator-friendly, and commitizen-compatible — all at once.
Getting started
Installation
uv add commitizen-spdx-changelog
# or: pip install commitizen-spdx-changelog
See the docs landing page for a full overview, and the usage guide for further setup and workflow instructions.
Configuration
In pyproject.toml:
[tool.commitizen]
changelog_format = "spdx-markdown"
Usage
cz bump --changelog
The plugin handles changelogs with SPDX frontmatter like:
---
# SPDX-FileCopyrightText: 2026 Pablo Hörtner <redtux@pm.me>
#
# SPDX-License-Identifier: Apache-2.0
icon: lucide/git-commit-vertical
---
# Changelog
## 0.4.0 (2026-06-08)
...
Development
direnv allow
uv sync --group dev
Running direnv allow will activate the devbox environment automatically. See
the Devbox guide for all available commands and tools.
Contributing
Bug reports, feature requests, and pull requests are welcome.
See contributing for guidelines.
For documentation contributions, please follow these principles:
Write for humans, keep it minimal, update docs with code, delete dead content.
Every page in docs/ and the project README.md are held to these standards.
License
Copyright © 2026 Pablo Hörtner
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at <http://www.apache.org/licenses/LICENSE-2.0>.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Metadata
Release files for commitizen-spdx-changelog 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| commitizen_spdx_changelog-0.1.4.tar.gz | 5.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| commitizen_spdx_changelog-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.9 kB
Release files / commitizen_spdx_changelog-0.1.4.tar.gz
| Download URL | commitizen_spdx_changelog-0.1.4.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ef40aa933b5cc838d79167aaa96f61449aade129a94a73bb690de3cbeb03562
|
|
BLAKE2b-256 checksum How to use checksums |
85385d1fc319bed164dfee1d932d0e1004b68c12baa1e7a6efebd4a13fe93e42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 25, 2026.
Transparency logRelease files / commitizen_spdx_changelog-0.1.4-py3-none-any.whl
| Download URL | commitizen_spdx_changelog-0.1.4-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30473e3cc18c4ff4ba624e8a5f3cf125c5e6d7bc068ccf17fae3d4e91cf7ce37
|
|
BLAKE2b-256 checksum How to use checksums |
95320e01db82bf6672ce9a362abc3e0fdd076a65b9b70b550a319e5c9bb90bcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 25, 2026.
Transparency log