Notification of PATCH updates: openapi.json file

Governance
1

Hi all,

I have prepared two PATCHes for HSDS which I intend to merge after 7 days if I do not receive any objections.

These PATCHes each fix the problem that the openapi.json file, which encodes the API Specification, was referring to schemas in the 3.0 branch of HSDS. Since we’re now on 3.2, I’m sure you can agree that wasn’t ideal.

Each PATCH effectively makes the same change, but does so separately for each 3.1 and 3.2. This means that Profiles, tooling, etc that was based on the older 3.1 branch benefit from the bugfix.

I’ve raised the PATCHes as PRs, and as always I encourage you to ask questions, raise objections etc. If I receive no objections in 7 days (2026-02-17), I’ll proceed with merging these into their respective branches. This will result in two new releases: 3.1.2 and 3.2.2, based on the updated 3.1 and 3.2 branches respectively.

  • #580 – Bugfix for the 3.2 branch
  • #581 – Bugfix for the 3.1 branch

Thanks,
Matt

2

These have been merged into their respective branches, with two new PATCH releases for each MINOR series: