fix(deps): update dependency openapi-python-client to >=0.28.1,<0.29.0 #117
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.
This PR contains the following updates:
>=0.24.3,<0.25.0→>=0.28.1,<0.29.0Release Notes
openapi-generators/openapi-python-client (openapi-python-client)
v0.28.1Compare Source
Fixes
v0.28.0Compare Source
Breaking Changes
Fixes
Fix bad code generation
##1360 by @EricAtORS
This fixes:
#1338 #1318
##931 and #1051
Fix optional bodies
If a body is not required (the default), it will now:
Unsetas part of its type annotation.UNSETUNSETThanks @orelmaliach for the report! Fixes #1354
v0.27.1Compare Source
Fixes
Update
uv_buildto 0.9##1352 by @johnthagen
uvhas been in the0.9.xrelease cycle for a while, so update templates to use the correspondinguv_buildrange.v0.27.0Compare Source
Breaking Changes
Drop support for Python 3.9
Both
openapi-python-clientitself and any generated clients no longer support Python 3.9.Generated models now use
from __future__ import annotationsThis simplifies using forward references with the newer union syntax.
Features
Upgrade generated clients to 3.10 union syntax
All generated types now use the
A | Bsyntax instead ofUnion[A, B]orOptional[A].Fixes
requires-pythonupper bounds for uv and PDM (#1329)Change default Ruff hook to
--fix-onlyThis should enable
openapi-python-clientto keep auto-fixing lints (like removing unused imports) but not fail togenerate when unfixable lints are violated.
Since it's now unlikely for breaking changes to affect our usage (and by popular request), the upper bound of
ruffhas been lifted. Newer versions of
openapi-python-clientshould no longer be required to support newer versions ofruff.Notes
v0.26.2Compare Source
Fixes
--meta=uv(#1321)v0.26.1Compare Source
Features
v0.26.0Compare Source
Breaking Changes
Change some union variant names
When creating a union with
oneOf,anyOf, or a list oftype, the name of each variant used to betype_{index}where the index is based on the order of the types in the union.
This made some modules difficult to understand, what is a
my_type_type_0after all?It also meant that reordering union members, while not a breaking change to the API, would be a breaking change
for generated clients.
Now, if an individual variant has a
titleattribute, thattitlewill be used in the name instead.This is only an enhancement for documents which use
titlein union variants, and only a breaking change forinline models (not
#/components/schemaswhich should already have used more descriptive names).Thanks @wallagib for PR #962!
Features
Support patterned and default HTTP statuses
HTTP statuses like
2XXanddefaultare now supported!A big thank you to:
Closes #1271 and #832
v0.25.3Compare Source
Features
uv_buildbuild backend. (#1290)v0.25.2Compare Source
Fixes
types.FileType(#1274) (#1278)v0.25.1Compare Source
Fixes
v0.25.0Compare Source
Breaking Changes
Removed ability to set an array as a multipart body
Previously, when defining a request's body as
multipart/form-data, the generator would attempt to generate codefor both
objectschemas andarrayschemas. However, most arrays could not generate valid multipart bodies, asthere would be no field names (required to set the
Content-Dispositionheaders).The code to generate any body for
multipart/form-datawhere the schema isarrayhas been removed, and any suchbodies will be skipped. This is not expected to be a breaking change in practice, since the code generated would
probably never work.
If you have a use-case for
multipart/form-datawith anarrayschema, please open a new discussion with an example schema and the desired functional Python code.Change default multipart array serialization
Previously, any arrays of values in a
multipart/form-databody would be serialized as anapplication/jsonpart.This matches the default behavior specified by OpenAPI and supports arrays of files (
binaryformat strings).However, because this generator doesn't yet support specifying
encodingper property, this may result innow-incorrect code when the encoding was explicitly set to
application/jsonfor arrays of scalar values.PR #938 fixes #692. Thanks @micha91 for the fix, @ratgen and @FabianSchurig for testing, and @davidlizeng for the original report... many years ago 😅.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.