# Action: Approval for HSDS 3.3

**URL:** <https://forum.openreferral.org/t/action-approval-for-hsds-3-3/855>\
**Category:** Technical Committee\
**Created:** [July 17, 2026, 10:49am UTC](https://forum.openreferral.org/t/action-approval-for-hsds-3-3/855 "2026-07-17T10:49:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrshll](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@mrshll](https://forum.openreferral.org/u/mrshll)\
**Post date:** [July 17, 2026, 10:49am UTC](https://forum.openreferral.org/t/action-approval-for-hsds-3-3/855/1 "2026-07-17T10:49:35Z")

</div>

Following the committee’s decision to approve two proposals on 2026-07-16, I have implemented these in a staging branch and raised a pull request to merge them into the new `3.3-dev` branch. There is an accompanying docs build for this branch as well:

- [PR #594](https://github.com/openreferral/specification/pull/594) which is staged to merge into `3.3-dev`
- [Docs build for `feature-schedule-groups-and-events`](http://docs.openreferral.org/en/feature-schedule-groups-and-events/)

In order to enact this change, I also needed to make some changes to the repo’s `requirements.in` and `requirements.txt` files to support the deprecation behaving nicely with the libraries we use to generate the docs.

If the committee approves this Pull Request, this will trigger a MINOR release of HSDS and the following things will happen:

1. I will merge `feature-schedule-groups-and-events` into the `3.3-dev` branch
2. I will rename `3.3-dev` to `3.3`
3. I will issue a new release entitled `v3.3`, based on the new `3.3` branch
4. I will update the repository’s default branch to `3.3`

---

<div class="post-metadata">

**Author:** ![mrshll](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@mrshll](https://forum.openreferral.org/u/mrshll)\
**Post date:** [August 4, 2026, 7:10am UTC](https://forum.openreferral.org/t/action-approval-for-hsds-3-3/855/2 "2026-08-04T07:10:20Z")

</div>

Bump. I need approval from another Committee member before I can merge and release the changes.

The task is to check that my schema and documentation changes in the PR are representative of what the committee agreed to accept in the following proposals:

- [service.operating\_hours and service.events](https://docs.google.com/document/d/1z4BF8w-slDu69cQ9IFak3kLYnJSSjSlBmdrU3OPxnYc/edit?tab=t.0#heading=h.ye0dggmm63xe)
- [Schedule groups](https://docs.google.com/document/d/15ioyklDOWVJnKrp0K-Rs3sbsFmw1oXHzR05yMMh_K9Q/edit?tab=t.0#heading)

@bloom @devin @skyleryoung @MikeThacker-iStandUK @oughnic @klambacher

---

<div class="post-metadata">

**Author:** ![mrshll](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@mrshll](https://forum.openreferral.org/u/mrshll)\
**Post date:** [August 19, 2026, 9:37am UTC](https://forum.openreferral.org/t/action-approval-for-hsds-3-3/855/3 "2026-08-19T09:37:10Z")

</div>

@oughnic and I met today (2026-08-19) to go through the Proposals and the PR. @oughnic approved so I:

- Merged #594 into the `3.3-dev` branch
- Renamed `3.3-dev` to `3.3`
- Issued the [v3.3 release](https://github.com/openreferral/specification/releases/tag/v3.3)
- Made the `3.3` branch the default branch of the repository

The `latest` branch of the docs is still playing catch-up, I will be monitoring this and will manually prod it along if it looks like it continues to lag.

---

<div class="post-metadata">

**Author:** ![oughnic](https://avatars.discourse-cdn.com/v4/letter/o/7feea3/32.png) [@oughnic](https://forum.openreferral.org/u/oughnic)\
**Post date:** [August 19, 2026, 9:59am UTC](https://forum.openreferral.org/t/action-approval-for-hsds-3-3/855/4 "2026-08-19T09:59:38Z")

</div>

Confirmed - I’m happy that the requirements are met by the implementation