-
Notifications
You must be signed in to change notification settings - Fork 301
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
Update dependency Django to v4.2.18 [SECURITY] (develop) #6780
Update dependency Django to v4.2.18 [SECURITY] (develop) #6780
Conversation
a3925c2
to
252d2e4
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
poetry.lock
Outdated
@@ -1,11 +1,12 @@ | |||
# This file is automatically @generated by Poetry 1.8.4 and should not be changed by hand. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't seem to downgrade my poetry version from 2.0.1 to 1.8.4. I wonder if this matters since we are going to upgrade to poetry 2.x eventually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might have to uninstall and reinstall, or use a tool like pipx
to have them coexist for now. It looks like this file is considered acceptable under Poetry 1.x even with these additions but I'd prefer to avoid making that change here unnecessarily.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Used poetry 1.8.4 to update the poetry.lock file, should be good now.
This PR contains the following updates:
4.2.17
->4.2.18
GitHub Vulnerability Alerts
CVE-2024-56374
An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions
clean_ipv6_address
andis_valid_ipv6_address
are vulnerable, as is thedjango.forms.GenericIPAddressField
form field. (The django.db.models.GenericIPAddressField model field is not affected.)Release Notes
django/django (Django)
v4.2.18
Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.