v0.9.4

0.9.4 (2026-09-17)

🚀 Feature

Show whether a breaking change applies to main or the latest release

The change-classification action reads the new release_impact decision field and shows it next to the default-branch impact. A package that breaks only against main (its latest release never shipped the changed API) renders as breaking → additive (release) in the comment table, gets an informational callout naming the package, and appears in the job summary line. The new release-breaking output is true only when a package breaks against its latest release, so workflow routing can block those pulls without blocking refinements of unreleased APIs.

Reports from monochange versions without release_impact render exactly as before.

- id: classify
  uses: monochange/actions/change-classification@v0

- run: |
    if [[ "${{ steps.classify.outputs.release-breaking }}" == "true" ]]; then
      echo "A released API broke; a major changeset is required."
    fi

Owner: @ifiokjr · Review: PR #70

Skip classification on release pull requests and pass labels

The change-classification action reads the pull request's labels (or the new labels input) and passes them to monochange change classify via --label. Configure [changesets.classification].skip_labels in monochange.toml (default ["release"]) so the release pull request monochange opens is reported as skipped instead of classified: the command analyzes no packages, the action sets result: skipped, deletes any stale classification comment, and the job summary records the skip.

The parser also accepts the classification report's new contract: snake_case keys with schema_version as a major.minor string emitted by monochange_classification.

- uses: monochange/actions/change-classification@v0
  with:
    labels: release, automated

Owner: @ifiokjr · Review: PR #68