Skip to content

fix(deps): update dependency drf-spectacular to ^0.29.0#2734

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/drf-spectacular-0.x
Open

fix(deps): update dependency drf-spectacular to ^0.29.0#2734
renovate[bot] wants to merge 1 commit intomainfrom
renovate/drf-spectacular-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 25, 2025

This PR contains the following updates:

Package Change Age Confidence
drf-spectacular ^0.28.0^0.29.0 age confidence

Release Notes

tfranzel/drf-spectacular (drf-spectacular)

v0.29.0

Compare Source

  • Add l18n handling for Decimal field #&#8203;1466 <https://github.com/tfranzel/drf-spectacular/issues/1466>_
  • Fix LogoutSerializer for JWT/dj_rest_auth #&#8203;1392 <https://github.com/tfranzel/drf-spectacular/issues/1392>_
  • fix: support token blacklist feature in rest_auth [Bart van Andel]
  • [django-filter] Add null_label if set in ChoiceFilter (#&#8203;1450 <https://github.com/tfranzel/drf-spectacular/issues/1450>_) [Enric Pou]
  • fix: camelize tuples/fixed length array (#&#8203;1432 <https://github.com/tfranzel/drf-spectacular/issues/1432>_) [Chris Wesseling]
  • Fix items:False case in enum hook #&#8203;1432 <https://github.com/tfranzel/drf-spectacular/issues/1432>_
  • Add option to overwrite serializer description #&#8203;1463 <https://github.com/tfranzel/drf-spectacular/issues/1463>_
  • Fix OpenApiViewExtension not providing view instance under self.target (#&#8203;1405 <https://github.com/tfranzel/drf-spectacular/issues/1405>_) [astro-stan]
  • Move list default fix to source of the problem #&#8203;1436 <https://github.com/tfranzel/drf-spectacular/issues/1436>_
  • Improve confusing doc #&#8203;1461 <https://github.com/tfranzel/drf-spectacular/issues/1461>_
  • Add assert to pagination test #&#8203;1459 <https://github.com/tfranzel/drf-spectacular/issues/1459>_
  • fix SafeString handling for picky CDumper (#&#8203;1435 <https://github.com/tfranzel/drf-spectacular/issues/1435>_)
  • Remove EOL 3.7 from suite; pydantic not updated for <=3.8
  • Fix DecimalField with decimal_places and max_digits equal. [keter2002]
  • fix test for i18n changes on DRF (#&#8203;1444 <https://github.com/tfranzel/drf-spectacular/issues/1444>_)
  • Improve to_filter_name support for django_filter [Matwey V. Kornilov]
  • fixes prefix estimation on windows [Luis Nell]
  • Fix default for array types [Stanislav Khlud]
  • fix: use CSafeDumper for render yaml if available [florian]
  • fix: sort list to produce same hash [florian]
  • Add typing.Generic to default lib_doc_excludes [Max Howald]
  • Add get_doc test for class that inherits from Generic [Max Howald]
  • Add Django REST framework 3.16 support [Paolo Melchiorre]
  • Fix memory leak [artemkucher]
  • Fix python 3.11 slice index [Egor Litvinov]
  • fix: correct port mapping for the container in README [Maksym Bieńkowski]
  • Update docs [q0w]
  • Allow setting callable for ENUM_NAME_OVERRIDES [q0w]
  • Add allauth's DRF token auth #&#8203;1401 <https://github.com/tfranzel/drf-spectacular/issues/1401>_
  • update away from retired GH worker image
  • add condition to check, that serializer Meta has model attribute [aliev_vt]
  • Fix docs compile issue and update some old code (#&#8203;1389 <https://github.com/tfranzel/drf-spectacular/issues/1389>_) [Mike Manger]
  • Fix location of @​extend_schema_field [johnthagen]
  • Remove reference to non-exposed lazy_serializer [johnthagen]
  • Document how to lazily define a recursive SerializerMethod [johnthagen]
  • Link to SerializerMethod docs [johnthagen]
  • Document Django 5.1 support in README [johnthagen]
  • Bump django from 4.2.11 to 4.2.18 in /requirements [dependabot[bot]]
  • Enhance bug report template with instructions for better clarity [antoliny0919]
  • add pydantic computed field to tests #&#8203;1354 <https://github.com/tfranzel/drf-spectacular/issues/1354>_

Breaking changes / important additions:

  • Finally fixed the memory leak thanks to @​artKucher.
  • Another performance improvement is the usage of the C versions of yaml, if available.
  • Apart from that, there are a lot of small improvements and bugfixes.

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/drf-spectacular-0.x branch 4 times, most recently from 1002acb to b3baeec Compare December 1, 2025 16:11
@renovate renovate bot force-pushed the renovate/drf-spectacular-0.x branch 13 times, most recently from 01be626 to 7279d20 Compare December 12, 2025 21:18
@renovate renovate bot force-pushed the renovate/drf-spectacular-0.x branch 12 times, most recently from 87252cd to ad804ca Compare December 18, 2025 03:55
@renovate renovate bot force-pushed the renovate/drf-spectacular-0.x branch 13 times, most recently from f3c0f9d to 36de0a9 Compare February 6, 2026 18:40
drf-nested-routers = "^0.95.0"
drf-spectacular = "^0.28.0"
drf-spectacular = "^0.29.0"
feedparser = "^6.0.10"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The custom CustomDjangoFilterExtension uses fragile positional argument access (args[4]) in resolve_filter_field, which will likely break due to refactoring in drf-spectacular 0.29.0.
Severity: HIGH

Suggested Fix

Refactor the resolve_filter_field method in main/schema.py to use keyword arguments instead of positional arguments. Inspect the method signature in drf-spectacular 0.29.0 to identify the correct parameter names and update the implementation to access them safely, removing the dependency on argument order.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: pyproject.toml#L52

Potential issue: The `CustomDjangoFilterExtension` in `main/schema.py` overrides the
`resolve_filter_field` method and accesses the fifth positional argument via `args[4]`.
This implementation assumes a fixed method signature. The `drf-spectacular` 0.29.0
release notes state that the django-filter extension was significantly refactored. If
the signature of `resolve_filter_field` has changed in the new version, accessing
`args[4]` could lead to an `IndexError` or incorrect behavior during OpenAPI schema
generation. This would cause a runtime failure when the API schema is accessed.

Did we get this right? 👍 / 👎 to inform future reviews.

@renovate renovate bot force-pushed the renovate/drf-spectacular-0.x branch 14 times, most recently from 1a78637 to 6a781a8 Compare February 11, 2026 19:47
@renovate renovate bot force-pushed the renovate/drf-spectacular-0.x branch from 6a781a8 to 257f828 Compare February 15, 2026 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants