v3.2.1 release

[karenetheridge]

This issue requires TSC signoff in order to complete.

• schema changes since last schema release (2025-11-23) consist of various fixes to be better aligned with the specification:

  • contentType format fix (now allows comma-separated values)
  • propertyName is required in the discriminator object
  • ABNF applied for path parameter names, header names, request method names
  • style, explode, allowReserved existence and defaults now better enforced
  • adjacent query, querystring parameters are prohibited

• spec changes since 3.2.0 release:

  • more cross-references to RFCs and other sections of the specification
  • clarification of how paths are matched when a template variable contains a "/"
  • corrections to the table of Style Examples (used in parameter encoding)
  • we now explicitly note more in/style/explode combinations that are prohibited, namely:
    • in: cookie, style: form, explode: false with arrays or objects
    • style: form, explode: true with arrays or objects in encoding objects (application/x-www-form-urlencoded or multipart/* message bodies)
  • corrections to descriptions of how encoding objects are used, such as the use of prefixEncoding and itemEncoding with data modelled as an array, and usage of contentType together or separately from a Content-Type header in a message part
  • addition of an ABNF for the encoding/contentType field

[miqui]

TSC votes:

• Yes, Miguel

Request was made to TSC slack thread as well.

[lornajane]

A yes vote from me!

[earth2marsh]

Thanks for the summary of changes. They all sound good, and given that patch releases are meant to be small in nature, I'm happy to give a yes vote to move the process forward. 👍

As an aside, one thing that I'm not confident I understand is where the biggest risks might be in this release. (I won't hold up the approval process for that, but in general I always like the case against to be given along with the high level framing of why people should appreciate the patch.)