v3.2: ports from 3.3 (June/July 2026)#5420
Open
karenetheridge wants to merge 13 commits into
Open
Conversation
karenetheridge
force-pushed
the
ether/v3.2-ports-from-3.3-202606
branch
from
0a5b864 to
a5edad7
Compare
…rmat (OAI#5332) In JSON, property keys are always strings; in YAML they may or not be depending on the parser, but other formats may also be in use (TOML, TOON etc). What matters is the resulting type(s) of the decoded data, not the specific formatting used for the serialized form.
Appendix D no longer talks about percent-encoding of headers, as the specification is now clear that percent-encoding of headers is never done (with the exception of the use of style:form in Cookie headers).
We are specifically talking about the "encoding" keyword here, and the multipart/form-data media-type (most other multipart types decode to arrays).
This change is accompanied by an edit to the "Forms" page in the Media-Type Registry.
We have the names for each part, as the parsed data uses the format:
[
{ <name>: <value> },
{ <name>: <value> },
...
]
..and be more specific about what an "array property" and "array schema" are
karenetheridge
force-pushed
the
ether/v3.2-ports-from-3.3-202606
branch
from
71bc187 to
e59e3a8
Compare
Member
Author
|
All the source PRs from v3.3 have been merged now, so this is ready to go. I edited each commit to indicate the original PR it came from. |
Member
Author
Member
|
@karenetheridge Were there any merge conflicts when porting these that you had to resolve? |
Member
Author
|
No conflicts. |
miqui
approved these changes
Jul 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Backports from 3.3 to 3.2 of recent spec edits.
Will continue populating this list until all 3.3 PRs are merged.
I think all of these are suitable for inclusion into 3.2.1, as they are all clarifications rather than introducing new capabilities.