fix: Render Django 6.1 breadcrumb markup on the alias usage page

[fsbraun]

Summary by Sourcery

Support Django 6.1 breadcrumb styling on the alias usage page while maintaining compatibility with earlier Django releases.

Bug Fixes:

• Render alias usage breadcrumbs with Django 6.1-compatible ordered-list markup while preserving the legacy layout for earlier Django versions.

Enhancements:

• Add a reusable template tag for Django version comparisons and cover version-dependent breadcrumb rendering with tests.

Build:

• Add Django 6.1 package support and dependency matrices across supported Python and django-cms combinations.

CI:

• Expand the tox test environment matrix to run Django 6.1 configurations.

Tests:

• Add coverage for the Django version comparison tag and alias usage breadcrumb markup across Django versions.

Claude-Session: https://claude.ai/code/session_01GwNaBKq7MNLhibbjjiAYHM

Related resources

• Fixes Alias usage page renders unstyled breadcrumbs on Django 6.1 #395
• #...

Checklist

• I have added or modified the tests when changing logic
• I have followed the conventional commits guidelines to add meaningful information into the changelog
• I have read the contribution guidelines

[sourcery-ai]

Reviewer's Guide

The PR fixes alias usage breadcrumbs across Django versions by adding a reusable version-checking template tag and conditionally rendering the Django 6.1+ ordered-list breadcrumb structure versus the legacy markup, with tests covering both version logic and generated HTML.

Flow diagram for version-aware alias usage breadcrumbs

flowchart TD
    A[Alias usage page renders breadcrumbs] --> B[django_version_gte 6 1]
    B -->|true| C[Render ol.breadcrumbs with li items]
    B -->|false| D[Render div.breadcrumbs with separators]
    C --> E[Display Usage of alias]
    D --> E

Loading

File-Level Changes

Change	Details	Files
Add Django-version-aware breadcrumb rendering for the alias usage page.	Introduce a template tag that compares the running Django major/minor version. Render Django 6.1+ breadcrumbs as an ordered list with current-page semantics, while retaining legacy div markup and separators for older versions.	djangocms_alias/templates/djangocms_alias/alias_usage.html djangocms_alias/templatetags/djangocms_alias_tags.py
Add coverage for version detection and rendered breadcrumb markup.	Test version comparisons at current, previous, next-minor, and next-major versions. Render the alias usage template directly and assert the appropriate markup and separator behavior for Django before and from 6.1.	tests/test_templatetags.py tests/test_views.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#395	Render Django 6.1-compatible breadcrumbs on the alias usage page using with list items, generated separators, and aria-current="page" on the final crumb.	✅
#395	Preserve the existing markup for Django versions before 6.1 so the page remains compatible with older supported Django releases.	✅
#395	Provide test coverage for the Django-version-dependent breadcrumb markup and the version comparison template tag.	✅

Possibly linked issues

• Alias usage page renders unstyled breadcrumbs on Django 6.1 #395: The PR directly fixes issue Alias usage page renders unstyled breadcrumbs on Django 6.1 #395 by switching to ol.breadcrumbs on Django 6.1 while preserving older markup.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}