Skip to content

Conversation

@szokeasaurusrex
Copy link
Member

Description

Add a new CI workflow that prevents manual CHANGELOG.md modifications unless the PR title starts with meta(changelog):.

This is a follow-up to #3074 which removed DangerJS. Now that changelogs are auto-generated, we need to prevent accidental manual edits. When a violation is detected, the workflow posts a comment explaining the policy and fails the check.

The workflow:

  • Checks if CHANGELOG.md is modified in the PR
  • Allows changes only when PR title starts with meta(changelog):
  • Posts an explanatory comment on violation (with duplicate detection)
  • Fails the CI check to block the PR

Issues

Add a new workflow that checks PRs for CHANGELOG.md modifications and
fails unless the PR title starts with `meta(changelog):`. When a
violation is detected, posts a comment explaining the automated
changelog policy and what action to take.

Fixes #3072
Co-Authored-By: Claude <[email protected]>
@szokeasaurusrex szokeasaurusrex requested a review from a team as a code owner January 12, 2026 16:14
@linear
Copy link

linear bot commented Jan 12, 2026

@szokeasaurusrex szokeasaurusrex marked this pull request as draft January 12, 2026 16:14
repo: context.repo.repo,
pull_number: prNumber,
per_page: 100
});
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing pagination allows CHANGELOG.md bypass in large PRs

Medium Severity

The listFiles call only fetches the first 100 files without handling pagination. If a PR modifies more than 100 files and CHANGELOG.md is not in the first page of results, the enforcement check will fail to detect it and allow the PR to merge without proper validation. This silently bypasses the intended changelog protection mechanism.

Fix in Cursor Fix in Web

owner: context.repo.owner,
repo: context.repo.repo,
issue_number: prNumber
});
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing pagination may cause duplicate warning comments

Low Severity

The listComments call doesn't specify per_page, using the default of 30. If a PR has more than 30 comments, the existing bot comment may not be found when checking for duplicates, causing repeated warning comments to be posted on subsequent workflow runs.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants