Skip to content

fix: handle informational messages from oasdiff v1.14.0#91

Merged
reuvenharrison merged 1 commit into
mainfrom
fix/handle-empty-breaking-message
Apr 12, 2026
Merged

fix: handle informational messages from oasdiff v1.14.0#91
reuvenharrison merged 1 commit into
mainfrom
fix/handle-empty-breaking-message

Conversation

@reuvenharrison

Copy link
Copy Markdown
Contributor

Summary

  • oasdiff v1.14.0 now prints "No changes to report, but the specs are different" when the diff is non-empty but no breaking/changelog entries are found (e.g. all suppressed via --err-ignore)
  • The entrypoint scripts treated any non-empty stdout as actual changes, which caused the ::notice:: upgrade link to fire incorrectly and output the wrong string
  • Fix: skip output lines starting with "No " — these are informational messages, not actual changes

Test plan

  • CI test oasdiff_breaking_err_ignore should pass (currently failing)
  • Verify no regression on other test scenarios

🤖 Generated with Claude Code

oasdiff v1.14.0 prints "No changes to report, but the specs are
different" when the diff is non-empty but no breaking/changelog entries
are found (e.g. all suppressed via --err-ignore). The entrypoint scripts
treated any non-empty output as actual changes, which caused the
::notice:: upgrade link to fire incorrectly and the wrong output string.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@reuvenharrison reuvenharrison merged commit f8cb930 into main Apr 12, 2026
24 checks passed
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.

1 participant