Update dependency openapi-python-client to >=0.29.1,<0.30.0 - #175
Open
renovate[bot] wants to merge 1 commit into
Open
Update dependency openapi-python-client to >=0.29.1,<0.30.0#175renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/openapi-python-client-0.x
branch
from
August 30, 2026 21:25
109de57 to
71c83d3
Compare
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.
This PR contains the following updates:
>=0.28.4,<0.29.0→>=0.29.1,<0.30.0Release Notes
openapi-generators/openapi-python-client (openapi-python-client)
v0.29.1Compare Source
🚨Security
Arbitrary code generation vulnerability
Prior to this release, malicious OpenAPI documents could cause openapi-python-client to generate arbitrary code, which
would then be executed by consumers of the generated client.
If you generate code from OpenAPI documents you don't control, you should upgrade to this release as soon as possible
and validate any previously-generated code.
See the GitHub advisory for more details.
🚀 Features
uv_buildto 0.12 when using--meta=uv(#1473)🐛 Fixes
StrEnumand-> Self(#1474)Fixed invalid Python identifiers when resolving naming conflicts
When two property or parameter names conflicted after conversion to
snake_case(e.g.foo-barandfooBar), the conflict-resolution path preserved delimiters like-,., and spaces in the generated Python identifiers, producing invalid code which failed generation. Conflicting names now keep their original casing but have any characters which are invalid in Python identifiers stripped (e.g.foobarandfooBar).Improve readability of error messages
Errors and warnings which include a snippet of your OpenAPI document now render that snippet as JSON, making them much easier to read.
📝Notes
Breaking changes for all custom templates
ALL custom templates are expected to break with this version as a result of the security fix.
utilsglobal has been renamed tostringsyou must describe how the value is being used so it can be properly escaped using either a Python function or Jinja filter:
strings.snake_case()/| snakecase(existing)strings.kebab_case()/| kebabcase(existing)strings.pascal_case()/| pascalcase(existing)python_identifier()(existing)class_name()(existing)strings.safe_for_docstring()/| safe_for_docstringfor values which get injected into a"""docstringstrings.in_f_string_literal()/| in_f_string_literalfor values that go intof""f-stringsstrings.in_double_quote_literal()/| in_double_quote_literalfor values that go into non-f-string""literals.as_unembedded_code()/| as_unembedded_codeONLY forPythonCodevalues—those that are intended to be Python code which is not embedded into any string/docstring. Examples include usages of.python_code,.get_type_string(),.get_instance_type_string(),.get_type_strings_in_union(). You should not assume these values are safe to put in docstrings, string literals, or f-string literals. Use the dedicated helpers for those.As always, you can check the diff of the built in templates for examples. You will also want to check generated output
for "UntrustedString", which is how any string now requiring one of those functions will appear.
Many control characters now stripped from string literals
Out of an abundance of caution, most Unicode control characters are now stripped from string literals.
If your API uses control characters as part of const values, enums, or JSON body property names you may have issues
with this new version.
Most APIs are not expected to be affected by this change.
v0.29.0Compare Source
Breaking Changes
Features
Fixes
Configuration
📅 Schedule: (UTC)
🚦 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.