fix: changelog provenance [skip ci] #11
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/changelog-provenance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fix a few issues with the changelog generation hack, and regenerate the changelog itself
Automated review by pr-reviewer v0.37.0 | Safety Check | Claude Sonnet 5 | tracking id
r-608e8f-67811eThis is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — Purely internal changelog-tooling refactor and regenerated changelog/doc content; no secrets, no production code changes, no obvious bugs.
This PR is a refactor of changelog tooling scripts plus a regenerated CHANGELOG.md and a new AGENTS.md note. Reviewing for anything alarming:
hack/changelog-lib.sh: consolidates shared helpers (require_changelog,repo_url,compare_link,replace_section_body) that were previously duplicated inupdate-changelog.shandbackfill-changelog.sh. The logic appears to be a faithful extraction — same awk pattern, same behavior, just deduplicated.CHANGELOGvar now defaults via${CHANGELOG:-CHANGELOG.md}, overridable for tests, which is reasonable.hack/enstubbify.shis a new script but only mutates CHANGELOG.md locally (git tag lookups, no network calls, no destructive git operations against remote). It requires a tag to exist before stubbing, which is a sane safety check.repo_urlexplicitly strips embedded credentials from the git remote URL before use — a good sign, not a red flag.Nothing here looks like an accidentally committed credential, a broken production code path, or a security issue. This is a safe, self-contained internal tooling change.