[skyc1e]

Explanation

git rev-list returns commits newest-first. The loop in updateChangelog
called .reverse() before iterating, but addChange uses unshift
(prepend) internally. The combination of reverse + unshift produced entries
in reverse chronological order (newest first).

Removing .reverse() lets unshift naturally reverse the newest-first
input into the correct oldest-first (forward chronological) order in the
changelog.

References

Fixes MetaMask/release-tools#117

Changelog

Fixed

• Changelog entries now appear in forward chronological order (earliest to latest)

Checklist

• Tests added to verify chronological ordering
• All 142 tests pass
• Lint and type check pass

---

Note

Low Risk
Small change to changelog generation order plus a focused test; low blast radius limited to release note formatting.

Overview
Ensures newly discovered commits are written to the changelog in forward chronological order (earliest first) by removing the extra .reverse() before adding entries.

Adds a regression test that mocks newest-first commit input and asserts the rendered changelog lists entries in the expected oldest-to-newest order.

^{Written by Cursor Bugbot for commit e55fb04. This will update automatically on new commits. Configure here.}

[GuillaumeRx]

This library has now been migrated into the release-tools monorepo. This PR has been locked and this repo will be archived shortly. Going forward, releases of this library will only include changes made in the release-tools repo.

• Please push this branch to release-tools and open a new PR there.
• Optionally, add a link pointing to the discussion in this PR to provide context.