Skip to content

3. Pro action, before #214 (changelog@v0.1.24) - #101

Open
oasdiff-test wants to merge 1 commit into
mainfrom
demo/pro-v0.1.24
Open

oasdiff-test wants to merge 1 commit into
mainfrom
demo/pro-v0.1.24

Conversation

@oasdiff-test

Copy link
Copy Markdown
Owner

Demo PR for comparing the oasdiff PR comment before and after oasdiff-action#214. Not for merging.

Runs oasdiff/oasdiff-action/changelog@v0.1.24, with an oasdiff-token (Pro), as the only oasdiff workflow on the branch, so the comment below is the one that action posted and nothing else.

The spec edit breaks clients four ways (a removed success response, a property that became required, a narrowed property type, a parameter that became required) and adds three optional properties and a version bump, so there is a mixed severity set for the comment to order. breaking reports the 3 at WARN and above; changelog reports all 11.

Four endpoint and schema edits that break clients, plus three added
optional properties and a version bump, so the comment has a mixed
severity set to order.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

📋 Review and approve the API changes

⏳ Review required: approve every change to make the oasdiff status check pass.

🔒 The comparison is encrypted in CI before it's uploaded. The decryption key stays in this link's fragment (after the #), which browsers never send to a server, so oasdiff cannot read your specs.

Posted automatically by the oasdiff GitHub Action. The oasdiff status check passes once every change is approved; make it a required check to block merging.

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