Start 3.3.0 #4976
Closed
Start 3.3.0 #4976
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
ralfhandl
commented
Sep 20, 2025
ralfhandl
commented
- no schema changes are needed for this pull request
handrews
reviewed
Sep 20, 2025
| | Field Name | Type | Description | | ||
| | ---- | :----: | ---- | | ||
| | <a name="oas-version"></a>openapi | `string` | **REQUIRED**. This string MUST be the [version number](#versions-and-deprecation) of the OpenAPI Specification that the OpenAPI document uses. The `openapi` field SHOULD be used by tooling to interpret the OpenAPI document. This is _not_ related to the [`info.version`](#info-version) string, which describes the OpenAPI document's version. | | ||
| | <a name="oas-self"></a>$self | `string` | This string MUST be in the form of a URI reference as defined by [[RFC3986]] [Section 4.1](https://www.rfc-editor.org/rfc/rfc3986#section-4.1). The `$self` field provides the self-assigned URI of this document, which also serves as its base URI in accordance with [[RFC3986]] [Section 5.1.1](https://www.rfc-editor.org/rfc/rfc3986#section-5.1.1). Implementations MUST support identifying the targets of [API description URIs](#relative-references-in-api-description-uris) using the URI defined by this field when it is present. See [Establishing the Base URI](#establishing-the-base-uri) for the base URI behavior when `$self` is absent or relative, and see [Appendix F]((#appendix-f-examples-of-base-uri-determination-and-reference-resolution)) for examples of using `$self` to resolve references. | |
There was a problem hiding this comment.
I'd rather keep the initial 3.3 set-up commit separate from other fixes. It makes it a lot easier to diff along a specific release line and see what went in (which is something I do from time to time).
There was a problem hiding this comment.
Backed out the link fix.
Now we just have to remember to squash-merge this PR.
|
@ralfhandl could you please just rebase it into one commit and force-push? "We just have to remember to..." is unlikely to happen. |
handrews
requested changes
Sep 20, 2025
|
Given that we had to disable all the sync jobs for a git reason, I suggest that we might want to hold off on doing more or less anything on 3.3 for now |
|
Sorry, didn't mean to actually close the thing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.