Update metcalfc/changelog-generator action to v4.8.0 - #45
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/metcalfc-changelog-generator-4.x
branch
from
August 11, 2026 00:49
93db862 to
3fcfcea
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.6.2→v4.8.0Release Notes
metcalfc/changelog-generator (metcalfc/changelog-generator)
v4.8.0Compare Source
Highlights
Failed changelog generation now fails the step
If the changelog could not be generated — an unresolvable ref, any git error — the action printed an
::error::annotation and then exited 0. The step went green,outputs.changelogwas never set, and downstream steps consumed an empty string without anything indicating a problem.It now exits non-zero.
fetch: trueno longer intermittently fails on shallow checkoutsThe default fetch path chained two
git fetch --depth=1calls ahead ofgit fetch --unshallow. Each rewrites.git/shallowwhile the next has already read it, so git would intermittently abort with:Because
fetch: trueis the default and the exit code was being discarded, this produced a silently empty changelog rather than a visible failure. It was happening in this repository's own CI.Now a single fetch, requesting
--unshallowonly when the checkout is actually shallow.Testing
make testpreviously rannpm test || echo "no tests available", wherenpm testwasexit 1— it reported success unconditionally. The project now has a real suite coveringchangelog.shagainst live git fixtures, ref validation, the release scripts, and the builtdist/bundle as the runner executes it. Both fixes above were found by adding it.Full changelog
v4.7.0Compare Source
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.