Skip to content

chore(deps): update dependency django-debug-toolbar to v6#329

Open
descope[bot] wants to merge 1 commit into
mainfrom
renovate/django-debug-toolbar-6.x
Open

chore(deps): update dependency django-debug-toolbar to v6#329
descope[bot] wants to merge 1 commit into
mainfrom
renovate/django-debug-toolbar-6.x

Conversation

@descope

@descope descope Bot commented Aug 15, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change OpenSSF
django-debug-toolbar (changelog) dependency-groups major ==5.2.0 → ==6.3.0 OpenSSF Scorecard

Release Notes

django-commons/django-debug-toolbar (django-debug-toolbar)

v6.3.0

Compare Source

What's Changed

Changelog from docs:
  • Replaced requirements_dev.txt file for pyproject.toml support with dependency groups.
  • Updated ReadTheDocs Python version to 3.13.
  • Modernize some panel styles and colors.
  • Standardize use of time/duration units and labels across panels.
  • Added translations for Lithuanian, Turkish and Uzbek.
  • Update the translations.
  • Expose a py.typed marker file.
  • Updated RedirectsPanel to emit the deprecation warning when it’s used rather than on instantiation.
  • Highlighted the documentation about disabling the browser’s caching to ensure the latest static assets are used.
  • Fixed bug with CachePanel so the cache patching is only applied once.
  • Added debug_toolbar.store.CacheStore for storing toolbar data using Django’s cache framework. This provides persistence without requiring database migrations, and works with any cache backend (Memcached, Redis, database, file-based, etc.).
  • Added CACHE_BACKEND and CACHE_KEY_PREFIX settings to configure the CacheStore.

New Contributors

Full Changelog: django-commons/django-debug-toolbar@6.2.0...6.3.0

v6.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: django-commons/django-debug-toolbar@6.1.0...6.2.0

v6.1.0

Compare Source

What's Changed

See change log here

Commits:

New Contributors

Full Changes: django-commons/django-debug-toolbar@6.0.0...6.1.0

v6.0.0

Compare Source

Description

The v6.0.0 release of Django Debug Toolbar significantly revamps how panels for the toolbar work. Each panel will now persist its data in a store. A store can either be backed by various backends. The toolbar will support a memory and database backend to start.

The toolbar is now using Django's SafeExceptionReporterFilter.cleanse_setting() function to filter out sensitive information. Some data will be replaced with "********************". This is because the toolbar could be configured to write the request information to a persistent store such as a cache or database.

Django applications with basic installations are backwards compatible with this change. If there are hooks into the internals of the toolbar, such as DebugToolbar.store_id then it will be backwards incompatible.

Third-party panels will need updating. Any data that is stored in record_stats will need to be fetched back out from self.get_stats() before being able to be rendered. This is to support loading an instance of the toolbar from persisted data. A simple example of this transition can be found in debug_toolbar/panels/cache.py in PR 2138

How to upgrade
  • Changes required if the toolbar isn't installed entirely programmatically
    • If you experience RuntimeError: Model class debug_toolbar.models.HistoryEntry doesn't declare an explicit app_label and isn't in an application in INSTALLED_APPS, you need to remove the reference to the toolbar's urls in your urls.py file and MIDDLEWARE setting when the toolbar isn't in INSTALLED_APPS
  • If you have a custom panel, you'll need to adjust record_stats and use self.get_stats() to fetch data for rendering
  • If you'd like to use the database store, see TOOLBAR_STORE_CLASS for more info
Why did the internals change?

The Django Debug Toolbar is a popular package we did not want to block the community from pursuing the async path for Django applications. Writing the request data to a store better positions the toolbar for async projects. It also opens the door for it being usable in production as well with API integrations.

What's Changed

Full Changelog: django-commons/django-debug-toolbar@5.2.0...6.0.0

Acknowlegements

Thank you to all the contributors who made this release possible. Thank you to @​robhudson, @​matthiask, @​tim-schilling, @​salty-ivy and @​dr-rompecabezas for their support, development and reviews of the serializable toolbar changes. A special shout-out to @​matthiask for leading the Djangonaut Space Session 4 team of @​dr-rompecabezas, @​andoriyaprashant and @​blingblin-g.

Configuration

📅 Schedule: (in timezone Asia/Jerusalem)

  • 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: Never, 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 has been generated by Mend Renovate.

@descope descope Bot added the renovate label Aug 15, 2025
@descope descope Bot force-pushed the renovate/django-debug-toolbar-6.x branch from f0f7662 to 253e779 Compare November 20, 2025 21:28
@descope descope Bot force-pushed the renovate/django-debug-toolbar-6.x branch from 253e779 to 5fd1968 Compare January 21, 2026 20:18
@descope descope Bot force-pushed the renovate/django-debug-toolbar-6.x branch from 5fd1968 to 58ff977 Compare February 10, 2026 15:25
@descope

descope Bot commented Feb 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock
Command failed: uv lock --upgrade-package django-debug-toolbar
Using CPython 3.14.4 interpreter at: /opt/containerbase/tools/python/3.14.4/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.9.*'):
  ╰─▶ Because the requested Python version (>=3.9, <4.0) does not satisfy
      Python>=3.10 and django-debug-toolbar==6.3.0 depends on Python>=3.10, we
      can conclude that django-debug-toolbar==6.3.0 cannot be used.
      And because django-descope:dev depends on django-debug-toolbar==6.3.0
      and your project requires django-descope:dev, we can conclude that your
      project's requirements are unsatisfiable.

      hint: While the active Python version is 3.14, the resolution failed for
      other Python versions supported by your project. Consider limiting your
      project's supported Python versions using `requires-python`.

      hint: The `requires-python` value (>=3.9, <4.0) includes Python
      versions that are not supported by your dependencies (e.g.,
      django-debug-toolbar==6.3.0 only supports >=3.10). Consider using a more
      restrictive `requires-python` value (like >=3.10).

@descope descope Bot force-pushed the renovate/django-debug-toolbar-6.x branch from 58ff977 to a311164 Compare April 23, 2026 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants