Skip to content

fix(deps): update dependency django-guardian to v3 #2266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 27, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 27, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
django-guardian (changelog) ^2.4.0 -> ^3.0.0 age adoption passing confidence

Release Notes

django-guardian/django-guardian (django-guardian)

v3.0.0: Version 3.0.0 - "The phoenix" 🐦‍🔥

Compare Source

🐦‍🔥This release

This is the culmination of more than FIVE YEARS of commits by various dedicated people, and a lot of wrangling to resurrect django-guardian from the dead. It aims to bring guardian up to date with a new team of maintainers and hit reset on the project going forward - it also encompasses updates to be compatible with the latest, greatest versions of django.

📚 Documentation and ⌨️ Typing

Guardian now has static typing, plus check out the new-look docs 🤩
... thanks @​dpgraham4401 for some substantive contributions here!

🚀 Performance

There are numerous upgrades to performance that are included here. The majority of users should find performance to be neutral or upgraded 🐎🥇.

⚠️⚠️⚠️⚠️⚠️ WARNING ⚠️⚠️⚠️⚠️⚠️ Some alterations have been made that may affect performance. All were done for good reasons, all were reviewed carefully by the maintainers at the time. But frustratingly we have only a rudimentary benchmarks suite. This PR discusses one such possible scenario.

  • If you are running large scale, mission critical apps, then you should probably benchmark your application with this new version (or at the very least update just this, making it an easy rollback).
  • Your support to create a benchmarks suite is very welcome!

🔧 Why a Major version?

We're reasonably sure that this major version does not actually constitute any breaking changes. However, there's been a complete turnover of the maintenance team, and we're releasing some features which we didn't touch, review or participate in in any way (although all commits have been doubly reviewed when they were merged).

I've gone over to review this entire release as best as I can but without many days of deep introspection, it's realistically possible to miss some changes that have implications deemed "breaking".

Sensible app developers should be pinning their dependencies like >2, <3 (or tighter) so in most cases, the update to this version (v3) will be a conscious choice as opposed to automatic update. It's therefore much safer for us to make a major version release (then possibly have to update the release notes!), than it is to do a minor version release which risks breaking people's systems.

To further mitigate this risk we'll first issue Release Candidate versions which people can install and give feedback on.

In the past, (eg the 2.0.0 release), removal of old django versions (which we have done in this release) was seen to be a breaking change. With modern dependency resolvers like uv and poetry this should no longer break people's installs (simply prevent them from using newer versions) so in future this will not be deemed a breaking change.

What's Changed

New Contributors

Full Changelog: django-guardian/django-guardian@v2.4.0...3.0.0


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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/django-guardian-3.x branch from dfd8bca to 7f19d80 Compare May 27, 2025 19:09
@renovate renovate bot force-pushed the renovate/django-guardian-3.x branch from 7f19d80 to 3ea0755 Compare May 27, 2025 19:15
@abeglova abeglova merged commit cd344b8 into main May 27, 2025
13 checks passed
@abeglova abeglova deleted the renovate/django-guardian-3.x branch May 27, 2025 19:28
@odlbot odlbot mentioned this pull request May 28, 2025
9 tasks
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.

1 participant