Skip to main content

release-creator

release-creator logo

PyPI Supported Python versions check

Release preparation tools for Python projects. The notes command renders a tagged changelog section for a GitHub Release. Other release tasks can use separate commands.

The documentation has a tutorial, how-to guides, a generated command reference, and an explanation of the changelog format.

Render GitHub Release notes

Run the current release from PyPI:

uvx --from 'release-creator' release-creator notes \
  --changelog docs/changelog.md \
  --tag 1.2.3 \
  --repository tox-dev/example \
  --previous 1.2.2 \
  --artifact-url https://pypi.org/project/example/1.2.3/ > release-notes.md

For automation, replace release-creator after --from with a tested release-creator==VERSION. The command reads the tagged section, maps Added to Features and Fixed to Bug fixes, changes linked author handles to GitHub mentions, and leaves bullets unwrapped. It keeps stable category anchors, omits empty categories when they are absent from the source, and adds artifact and comparison links. Use --artifact-label for an ecosystem other than PyPI; omit --artifact-url when there is no external artifact.

The command also accepts a .rst changelog with the same category names. For projects whose :issue: role points at PRs, pass --issue-role pull:

uvx --from 'release-creator' release-creator notes \
  --changelog docs/changelog.rst \
  --tag 1.2.3 \
  --repository tox-dev/example \
  --previous 1.2.2 \
  --issue-role pull \
  --artifact-url https://pypi.org/project/example/1.2.3/ > release-notes.md

The changelog is the source of truth. The command does not infer changes from commits or generate an author list. Add verified human credits to changelog entries before release; omit bot credits. The GitHub Release may add a New Contributors section by passing --generated-notes with the body from GitHub's generate-notes API. Human first-time contributors remain listed even when their PR did not need a changelog entry. The generated-notes banner and other generated sections are discarded.

Named Towncrier fragments need no issue or PR number. Before Towncrier builds the changelog, run release-creator fragments --repository owner/repo --git. The command reads each fragment's introducing squash commit, adds its PR link, and fails if the subject does not end in (#number). For a checkout without Git history, pass a tab-separated subject map with --commit-map commits.tsv instead.

The tags command calculates a version from pending fragments, validates numeric tags, and selects the preceding tag for GitHub comparisons:

git tag --list | uvx --from 'release-creator' release-creator tags --next auto
git tag --list | uvx --from 'release-creator' release-creator tags 1.2.3 --require-newer
git tag --list | uvx --from 'release-creator' release-creator tags 1.2.3 --previous

Development and releases

See contributing for the fragment format and release process. The package uses the same notes command for its own GitHub Releases. Run tox -e 3.15,type,pkg_meta,docs and prek run --all-files before a PR.

Metadata

Release files for release-creator 0.5.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for release-creator 0.5.1
File Size Uploaded Provenance
release_creator-0.5.1.tar.gz 158.6 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for release-creator 0.5.1
File Interpreter ABI Platform
release_creator-0.5.1-py3-none-any.whl Python 3 none any Details

Total release size: 209.6 kB

Release files / release_creator-0.5.1.tar.gz

Download URL release_creator-0.5.1.tar.gz
Size 158.6 kB
Tags Source
SHA-256 checksum
How to use checksums
755f8d460a493789756ab1bd4bbda0dd90145699288239085dd712cba2d84251
BLAKE2b-256 checksum
How to use checksums
65d383211b4ebfbaf87383392aed6ef3aa98d65e0ade613a2aa0ea0f222cb6b1
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 Oct 22, 2026.

Transparency log

Release files / release_creator-0.5.1-py3-none-any.whl

Download URL release_creator-0.5.1-py3-none-any.whl
Size 51.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7aa5f28c5195f6f5e0493abede9c041a58d015bc3a837feee5669cc2062d6053
BLAKE2b-256 checksum
How to use checksums
5f88fab14c09530c8691040ec040613476d645414e2db1123c35b3818d291cea
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 Oct 22, 2026.

Transparency log

Security for release-creator 0.5.1

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.

Select from 2 files

Attestation for release_creator-0.5.1.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 Oct 22, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page