This release adds components to entries, supports tagging during publish, and polishes release creation output while inverting the show table order.
💥 Breaking Changes
Section titled “💥 Breaking Changes”Invert show table order
Section titled “Invert show table order”Oct 22, 2025 · @mavam, @claude · #1
tenzir-changelog show now renders the primary changelog table with
backward-counting row numbers, so #1 consistently targets the newest change
while older entries climb toward the top.
The command also subsumes the old list/export split: use the default view
for the numbered table, -c/--card for rich panels, or -m/--markdown /
-j/--json to export releases, the unreleased bucket, or ad-hoc selections.
# Browse every entry with numbered rowsuvx tenzir-changelog show
# Inspect a specific change as a carduvx tenzir-changelog show -c 2
# Export an entire release (compact bullets optional)uvx tenzir-changelog show -m v0.2.0Cards highlight metadata, release status, and formatted Markdown together, so you can review and share entry details without juggling multiple commands.
🚀 Features
Section titled “🚀 Features”Add components to changelog entries
Section titled “Add components to changelog entries”Oct 26, 2025 · @codex
Entries can now record an optional component tag (for example cli, docs, or ci). If you skip the field—as we do in this repository—the CLI behaves exactly as before. When a component is present, tenzir-changelog show adds a dedicated column, release notes surface the label, and Markdown/JSON exports include the value.
Projects that want per-component slices can pass --component <name> to tenzir-changelog add and reuse the same flag on show when filtering a backlog or exporting a release.
Finally, the table view only renders the Component column when at least one entry in the result set uses the feature, keeping homogeneous changelog streams clutter-free.
Support tagging during release publish
Section titled “Support tagging during release publish”Oct 24, 2025 · @codex
Add a --tag flag to release publish so the command can create the annotated Git tag before invoking the GitHub workflow, logging a warning and skipping creation when the tag already exists.
🔧 Changes
Section titled “🔧 Changes”Polish release creation output
Section titled “Polish release creation output”Oct 25, 2025 · @codex
The release creation summary now shows the familiar emoji table alongside an inline list that reuses our logger glyphs, making it quicker to scan entries and confirm what will happen when finalizing a release.