Skip to content

Enforce that one of the changelog entries in a new release is marked as breaking if bumping to a major version #6825

@mcmire

Description

@mcmire

Problem

Some teams bump a package by a major but don't adequately call out breaking changes in the changelog when they do so. It is convention to mark these changes using a **BREAKING:** prefix. At least one of these entries should be present.

Acceptance Criteria

  • A release PR cannot be merged if a workspace package is being bumped by a major, but there is no entry present in the changelog for the new version with a **BREAKING:** prefix.
  • Bonus points if we write this in such a way that when Add bot comment to describe release spec warnings #5553 is implemented, the user will receive a bot comment that tells the user the error and shows them how to fix it.

Related issues

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions