Repository navigation
feat!: the API's spec at 1.0.0-preview.12 - #16
Merged
Merged
Conversation
haau3-bot
Bot
force-pushed
the
regenerate-spec
branch
from
October 21, 2026 01:18
24a3914 to
9a4f8fa
Compare
haau3-bot
Bot
changed the title
haau3-bot
Bot
changed the title
haau3-bot
Bot
force-pushed
the
regenerate-spec
branch
2 times, most recently
from
October 21, 2026 04:36
341fb4b to
d11baf4
Compare
haau3-bot
Bot
force-pushed
the
regenerate-spec
branch
from
October 21, 2026 15:28
d11baf4 to
7757650
Compare
haau3-bot
Bot
changed the title
haau3-bot
Bot
force-pushed
the
regenerate-spec
branch
from
October 21, 2026 20:11
7757650 to
18d34ab
Compare
haau3-bot
Bot
changed the title
haau3-bot
Bot
force-pushed
the
regenerate-spec
branch
2 times, most recently
from
October 22, 2026 15:26
c381c1f to
f376801
Compare
haau3-bot
Bot
force-pushed
the
regenerate-spec
branch
from
October 22, 2026 20:12
f376801 to
7aa40f7
Compare
haau3-bot
Bot
changed the title
Merged
briankfung
pushed a commit
that referenced
this pull request
Oct 23, 2026
The next release of haau3, from the pull requests merged since the last one. Merging this makes the GitHub Release and builds the version, which is published to PyPI once a maintainer approves it. --- ## [0.2.0](v0.1.4...v0.2.0) (2026-10-23) ### ⚠ BREAKING CHANGES * the API's spec at 1.0.0-preview.12 ([#16](#16)) ### Features * a header an operation declares is a keyword of its own ([#20](#20)) ([94e5ed2](94e5ed2)) * the API's spec at 1.0.0-preview.12 ([#16](#16)) ([303f24c](303f24c)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: haau3-bot[bot] <344534095+haau3-bot[bot]@users.noreply.github.com>
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
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.
The API's spec changed from
1.0.0-preview.6to1.0.0-preview.12, read from https://api.haau3.com/openapi.json with ETag"vKq9j9lwRsLuLLOcQsKvJ431si_".Merging this releases a minor version: oasdiff found 1 change that can break callers, listed below.
If a check fails, this spec needs a change by hand (a method the README calls is gone, say). Push the fix to this branch: haau3-bot never overwrites a commit it did not make.
The title becomes the line in CHANGELOG.md, so rewrite it in plain words if you like, keeping its prefix. Taking the
!out offeat!:releases a patch instead of a minor.Changes that can break callers (1)
GET /v1/fhir/r4/ValueSet/$expand: for thequeryrequest parameterfilter, the maxLength was set to500(request-parameter-max-length-set)Other changes (20)
POST /v1/fhir/r4/$process-message: added the new optionalheaderrequest parameterpayer-authorization(new-optional-request-parameter)POST /v1/fhir/r4/$process-message: added the non-success response with the status403(response-non-success-status-added)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parameter_include(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parameterlocation.address-city(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parameterlocation.address-postalcode(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parameterlocation.address-state(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parametername(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parameterorganization(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parameterorganization.identifier(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parameterservice-category(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the new optionalqueryrequest parameterspecialty(new-optional-request-parameter)GET /v1/fhir/r4/HealthcareService: added the non-success response with the status422(response-non-success-status-added)GET /v1/fhir/r4/InsurancePlan: api tagMedical Benefitsadded (api-tag-added)GET /v1/fhir/r4/InsurancePlan: api tagPlan Benefitsremoved (api-tag-removed)GET /v1/fhir/r4/InsurancePlan/$counties: api tagMedical Benefitsadded (api-tag-added)GET /v1/fhir/r4/InsurancePlan/$counties: api tagPlan Benefitsremoved (api-tag-removed)GET /v1/fhir/r4/InsurancePlan/{id}: api tagMedical Benefitsadded (api-tag-added)GET /v1/fhir/r4/InsurancePlan/{id}: api tagPlan Benefitsremoved (api-tag-removed)GET /v1/fhir/r4/InsurancePlan/{id}/$in-network: api tagMedical Benefitsadded (api-tag-added)GET /v1/fhir/r4/InsurancePlan/{id}/$in-network: api tagPlan Benefitsremoved (api-tag-removed)