chore(deps): update metcalfc/changelog-generator action to v4.9.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
metcalfc/changelog-generator	action	minor	v4.7.0 → v4.9.1

---

Release Notes

metcalfc/changelog-generator (metcalfc/changelog-generator)

v4.9.1

Compare Source

Patch release for the v4 line

Documentation and CI only. dist/ is byte-identical to
v4.9.0,
so there is no functional change for consumers; this release exists so the v4
tag points at a commit whose docs are correct.

• Return the modified changelog as a real multiline output (#​478)

The README's "Simple output modifications" recipe percent-encoded newlines as
%0A, which the long-removed ::set-output command decoded. $GITHUB_OUTPUT
does not, so anyone who copied that snippet got a single line with literal
%0A in it. It now uses the heredoc form, with a random delimiter because the
value is built from commit subjects.

The changelog output format remains unchanged from v4.8.0. See
v5.0.0
for the breaking change that renders commit subjects as literal text.

v4.9.0

Compare Source

Maintenance release for the v4 line

Security and dependency fixes only. The changelog output format is unchanged
from v4.8.0 -- verified byte-identical -- so tracking @v4 is safe.

• undici 7.29.0, closing all 12 open advisories (4 high)
• release-workflow hardening: tag names no longer reach a shell as source, and
  the published bundle is now verified against a rebuild before attestation
• @vercel/ncc 0.45.0 and dev-dependency bumps

v5.0.0
contains these same fixes plus a breaking change: commit subjects render as
literal text, so a merged pull request's subject can no longer inject links or
mentions into your release notes. That change also stops #123 autolinking
inside subjects, which is why it is not on the v4 line.

---

• 8b3d973 - 4.9.0
• ab3e266 - fix: carry the bump:workflow provenance fix onto the v4 line
• f6a78ba - release: prepare the v4 maintenance line
• 8becfce - fix(deps): bound the dependency overrides and clear the undici advisories (#​476)
• f723555 - build(deps-dev): bump @​vercel/ncc from 0.44.1 to 0.45.0 (#​470)
• 88097f8 - build(deps-dev): bump eslint from 10.8.1 to 10.9.0 (#​472)
• 430ccb9 - build(deps-dev): bump globals from 17.9.0 to 17.11.0 (#​471)
• d40422b - build(deps): bump the codeql-action group with 3 updates (#​469)
• ba35f7d - Verify release bundle before attestation (#​474)
• 91ac6bb - Render changelog subjects as literal text (#​475)
• c2ec39e - Keep release tag names out of shell source (#​473)
• b28b10d - ci: let the stale workflow be run on demand (#​467)
• d255efb - build(deps): bump actions/setup-node from 6.5.0 to 7.0.0 (#​463)
• 20397cc - build(deps): bump actions/checkout from 6.0.2 to 7.0.1 (#​450)
• 67da1d3 - build(deps): bump actions/stale from 10.2.0 to 11.0.0 (#​462)

v4.8.0

Compare 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.changelog was never set, and downstream steps consumed an empty string without anything indicating a problem.

It now exits non-zero.

[!WARNING]
This is a behavior change. A workflow that was quietly passing on a broken changelog will now fail. That is the point — but expect it to surface as new red builds rather than as new errors, since the errors were always being printed.

fetch: true no longer intermittently fails on shallow checkouts

The default fetch path chained two git fetch --depth=1 calls ahead of git fetch --unshallow. Each rewrites .git/shallow while the next has already read it, so git would intermittently abort with:

fatal: shallow file has changed since we read it

Because fetch: true is 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 --unshallow only when the checkout is actually shallow.

Testing

make test previously ran npm test || echo "no tests available", where npm test was exit 1 — it reported success unconditionally. The project now has a real suite covering changelog.sh against live git fixtures, ref validation, the release scripts, and the built dist/ bundle as the runner executes it. Both fixes above were found by adding it.

Full changelog

• 98b1282 - 4.8.0
• 32f61b2 - fix: make the version bump scripts portable (#​466)
• f64bf35 - build(deps-dev): bump eslint from 10.1.0 to 10.8.1 (#​460)
• e5f3244 - build(deps-dev): bump brace-expansion from 5.0.5 to 5.0.7 (#​448)
• 57d0aa3 - build(deps-dev): bump globals from 17.4.0 to 17.9.0 (#​457)
• ce20209 - build(deps-dev): bump prettier from 3.8.1 to 3.9.6 (#​454)
• 89d0cce - build(deps): bump actions/attest-build-provenance from 4.1.0 to 4.2.2 (#​464)
• daae4ab - build(deps): bump the codeql-action group with 3 updates (#​461)
• 58f7ad5 - fix: fail the step when the changelog cannot be generated (#​465)
• 4ffdab6 - build(deps-dev): bump @​vercel/ncc from 0.38.4 to 0.44.1 (#​441)
• ce7d426 - ci: bump codeql-action to v4.37.1 and group its future updates (#​459)
• cbc6a25 - test: replace the no-op test target with a real suite (#​458)
• f278f3b - docs: update README example to use actions/checkout v6
• 3f3af1f - fix: bump actions to Node 24-compatible versions
• 10c0451 - fix: pin codeql-action to SHA and document supply chain security

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

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

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.