Skip to content

build: ignore key order when verifying openapi specs - #270

Merged
paullatzelsperger merged 1 commit into
mainfrom
fix/verify_openapi_key_order
Oct 22, 2026
Merged

paullatzelsperger merged 1 commit into
mainfrom
fix/verify_openapi_key_order

Conversation

@paullatzelsperger

Copy link
Copy Markdown
Member

What this PR changes/adds

The verify-openapi workflow sorts the keys of both the published and the newly merged spec with yq before diffing them.

Why it does that

mergeOpenApiSpec does not produce a stable key order, so the merged spec can list the same paths and responses in a different order than the published one. The plain diff then fails PRs that do not touch the API at all (e.g. eclipse-edc/Connector#6150). Key order has no meaning in YAML maps, so sorting both sides only removes these false positives; actual changes to the spec are still reported.

Linked Issue(s)

none

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@paullatzelsperger
paullatzelsperger requested a review from a team as a code owner October 22, 2026 08:11
@paullatzelsperger
paullatzelsperger merged commit 5ac275e into main Oct 22, 2026
6 of 9 checks passed
@paullatzelsperger
paullatzelsperger deleted the fix/verify_openapi_key_order branch October 22, 2026 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants