Following the committee’s decision to approve a number of proposals on 2025-09-10, I have implemented the proposals and integrated them into a development branch called 3.2-dev on Github, which is now available for review. There is an accompanying docs build for review as well.
According to the governance process, I require approval from members of the Technical Committee to release this new version. Once it has been approved, the following will occur:
- I will wait until PATCH 3.1.2 has been merged into the
3.1branch and then rebase3.2-devon this, to ensure that we bring these changes through. - I will change the branch name from
3.2-devto3.2and make it the default branch in the specification repo. - I will issue a Github release using the tag
3.2
To support review, please consult the 3.2 changelog on the docs and compare these changes with what outlined in the following proposals (which were approved by the committee):
- Proposal: Marking OpenAPI Endpoints with Tags to match the HSDS API Specification
- Proposal: API Field for Linking to Data Guides
- Proposal: Extra metadata with API Feeds
More git-inclined folks may want to inspect the actual changes to the schema files and the openapi files:
- Comparison of 3.1 and 3.2-dev on Github which will show the cumulative changes to files.
I would appreciate confirmation of approval in this forum thread, if possible.