ci: restore changelog updates - #2074
Merged
bearomorphism merged 2 commits intoAug 20, 2026
Merged
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
Copy link
Copy Markdown
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## master #2074 +/- ##
=======================================
Coverage 98.26% 98.26%
=======================================
Files 61 61
Lines 2829 2829
=======================================
Hits 2780 2780
Misses 49 49 ☔ View full report in Codecov by Harness. |
Sorry, something went wrong.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
bearomorphism
force-pushed
the
bearomorphism-fix-changelog-pipeline
branch
from
54387b0 to
c391d9d
Compare
August 20, 2026 15:30
woile
reviewed
Aug 20, 2026
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
woile
approved these changes
Aug 20, 2026
Copy link
Copy Markdown
Collaborator
Author
|
Thanks for quick review! (I'm still reading the root cause analysis from AI) |
Sorry, something went wrong.
bearomorphism
commented
Aug 20, 2026
Comment thread
AGENTS.md
bearomorphism
marked this pull request as ready for review
August 20, 2026 15:47
Copy link
Copy Markdown
Contributor
🔍 Commitizen bump previewNo commits in this PR are eligible for a version bump. |
Sorry, something went wrong.
vemilano
pushed a commit
to vemilano/commitizen
that referenced
this pull request
Aug 24, 2026
* ci: restore changelog updates Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * ci: configure changelog updates on bump Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The release workflow stopped committing CHANGELOG.md after migrating from commitizen-action to setup-cz, because the replacement configuration no longer enabled changelog updates during cz bump. GitHub release notes continued to be generated into a temporary file, leaving the repository changelog stale after v4.13.9.
This enables changelog generation on bump, uses incremental generation to preserve historical manual edits, and backfills all 13 releases from v4.13.10 through v4.18.0. It also documents release-triggering Conventional Commit and PR title types for AI agents to prevent CI-only changes from causing patch releases.
Checklist
Was generative AI tooling used to co-author this PR?
Generated-by: GitHub Copilot following the guidelines
Code Changes
Documentation Changes
The repository changelog is backfilled from the existing release tags, and AGENTS.md now explains which commit and PR title types trigger releases.
Expected Behavior
Each successful automated version bump commits the new changelog entry to CHANGELOG.md. Incremental generation updates only releases newer than the latest version already present.
Steps to Test This Pull Request
Additional Context
The regression was introduced in PR #1924 by commit 97fb356d, which replaced commitizen-action (defaulting to --changelog) with a direct cz bump --yes invocation without the equivalent configuration.