3.3: initialize for minor release 3.3.0

[ralfhandl]

• Initialize src/oas.md from versions/3.2.0.md on the main branch with empty history
• Bump version to 3.3.0
• Restore @karenetheridge's change from fix a whitespace error #5004
• Bump version in schema files
• Bump version in schema tests

This PR's head branch was created with scripts/start-release.sh from

• main: new script to start a release #5034

---

• schema changes are included in this pull request

[miqui]

looks good @ralfhandl

[Copilot]

Pull Request Overview

This PR initializes the minor release 3.3.0 by bumping version numbers across the OpenAPI specification files and test cases. It prepares the codebase for the next version by updating version references from 3.2.x to 3.3.x throughout the project.

• Update all OpenAPI version references from 3.2.x to 3.3.x
• Bump schema validation patterns and URLs to use 3.3 namespace
• Update test cases and examples to reference version 3.3.0

Reviewed Changes

Copilot reviewed 62 out of 62 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
tests/schema/schema.test.mjs	Update test description and OpenAPI version in test fixture
tests/schema/pass/*.yaml	Bump OpenAPI version in all passing test cases from 3.2.x to 3.3.x
tests/schema/fail/*.yaml	Bump OpenAPI version in all failing test cases from 3.2.x to 3.3.x
src/schemas/validation/schema.yaml	Update schema ID, description, version pattern, and all spec references to 3.3
src/schemas/validation/schema-base.yaml	Update schema base ID, description, and references to 3.3
src/schemas/validation/meta.yaml	Update meta schema ID and vocabulary reference to 3.3
src/schemas/validation/dialect.yaml	Update dialect ID, title, description, and vocabulary references to 3.3
src/oas.md	Update specification version to 3.3.0 and add version history entries

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[mikekistler]

This looks good but I'm going to hold off approving until there is some explanation of the one instance of "3.3.1".

[mikekistler]

Why is this file "3.3.1" but all the others are "3.3.0"?

[ralfhandl]

This test case also tests a non-zero patch version number in the OpenAPI field, which should pass validation with a 3.3 schema, and it does.

[mikekistler]

So it is acceptable to use non-existent patch version numbers? So "3.3.987" also validates? That seems odd.

But if that's the case, can we add a comment in the file to make that clear?