Bump django-tree-queries from 0.22.0 to 0.23.0

[dependabot]

Bumps django-tree-queries from 0.22.0 to 0.23.0.

Changelog

Sourced from django-tree-queries's changelog.

Change log

Next version

0.23 (2025-11-27)

• Added a new OrderableTreeNode base class which includes a position field for ordering among siblings, and started recommending it.

0.22 (2025-11-06)

- Made the new ``tree_queries.admin`` module importable when
  ``django-js-asset`` isn't installed so that ``compilemessages`` and other
  tools automatically importing this module are allowed to work.
- Added an example migration to the documentation for migrating from
  django-mptt to django-tree-queries. Thanks to @felixmm for providing this!
- Avoided fetching ancestors of nodes without parents. Thanks to @felixmm!
- Added a system check which verifies that ``"tree_queries"`` has been added to
  ``INSTALLED_APPS`` if using the ``TreeAdmin`` model admin class.
0.21 (2025-09-16)

• Added the missing FieldDoesNotExist import. Thanks Kircheneer.
• Fixed all errors reported by pre-commit and started running hooks automatically.
• Added TreeAdmin class for Django admin with intuitive tree management, node moving capabilities, and support for both positioned and unpositioned trees. Requires django-js-asset which is included in the new admin extra.

0.20 (2025-06-11)

- Added Python 3.13, Django 5.1 and 5.2 to the testsuite.
- Added tests showing that ``.descendants().update(...)`` doesn't work, but
  ``.filter(pk__in=....descendants()).update(...)`` does.
- Added Python 3.13 to the testsuite.
- Converted the tests to use pytest.
- Added a ``tree_info`` template tag and a ``recursetree`` template block.
- Optimized the performance by avoiding the rank table altogether in the simple
  case of an ascending ordering on a single field. If that's not possible, the
  README now documents using ``.tree_filter()`` and ``.tree_exclude()`` to
</tr></table> 

... (truncated)

Commits

• 8358b13 django-tree-queries 0.23
• 6be8a54 Fix #101: Introduce an ordered tree node base class and recommend using it
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.