Skip to content

fix "openapi" field to accept 3.3 versions #5033

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

fix "openapi" field to accept 3.3 versions #5033

wants to merge 1 commit into from
+61 −61

Conversation

karenetheridge
Copy link
Member

  • schema changes are included in this pull request

@karenetheridge karenetheridge requested review from a team as code owners October 13, 2025 17:43
@karenetheridge karenetheridge added the Schema changes related to the schema(s) label Oct 13, 2025
@karenetheridge karenetheridge added this to the v3.3.0 milestone Oct 13, 2025
@ralfhandl
Copy link
Contributor

The version needs to be bumped in more places in all four schema files. I've got a script for that, included in PR

It also initializes the src/oas.md file from the last published version (now: 3.2.0), so if you run the in your branch, you'd have to cherry-pick your "fix a whitespace error" commit from the v3.3-dev branch.

Next time we should run the start-release.sh script right after merging the release into main and syncing it to the development branches, before we do any work on the subsequent release(s).

@karenetheridge karenetheridge deleted the ether/3.3-version branch October 14, 2025 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Schema changes related to the schema(s)

Projects

None yet

Milestone

v3.3.0

Development

Successfully merging this pull request may close these issues.

2 participants

@karenetheridge @ralfhandl