chore(deps): update metcalfc/changelog-generator action to v5 - #5655
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update metcalfc/changelog-generator action to v5#5655renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/metcalfc-changelog-generator-5.x
branch
from
August 31, 2026 14:37
e6b8dc7 to
4acf55b
Compare
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.
This PR contains the following updates:
v4.9.1→v5.0.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
metcalfc/changelog-generator (metcalfc/changelog-generator)
v5.0.1Compare Source
5.0.1Base the changelog on the previous release of the same line, and assert it (#​479)fix: return the modified changelog as a real multiline output (#​478)v5.0.0Compare Source
Breaking change: commit subjects render as literal text
Every changelog line now wraps the commit subject in an inline-code span.
A commit subject is untrusted input. Anyone whose pull request you merge
chooses that text, and this action pastes it directly into your release notes.
Rendered as active Markdown, a subject could contribute links, images,
@mentions, issue references, raw HTML, or additional changelog entries to arelease it had no business editing. Rendering it as literal text closes that
off.
What this costs you. Subjects render monospace, and
#123,GH-123, barecommit SHAs, and
:emoji:inside a subject no longer autolink. BecauseGitHub's squash merge appends
(#​123)to the subject by default, most linesin a typical repository lose that link. The generated commit link at the start
of each line is unaffected. Control characters, line and paragraph separators,
and bidirectional-control characters are replaced with spaces, so a subject can
never span more than its own line.
No inputs or outputs changed, and the
No Changes.sentinel is unchanged.Staying on the previous format
v4.9.0
carries every security and dependency fix in this release -- including undici
7.29.0, which closes 12 advisories -- with the v4 output format untouched. Pin
metcalfc/changelog-generator@v4to stay there. Thev4tag will keep movingon the maintenance line.
What is in this release
Relative to v4.9.0, v5.0.0 adds only the escaping change. Both releases share
everything else:
bump:workflowrewriting pinned actions' provenance comments (#477)@vercel/ncc(#470),eslint(#472),globals(#471),codeql-action(#469)Full history: v4.8.0...v5.0.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.