Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[back] sec: upgrade Django to 4.2.17 from 4.2.16 #2036

Merged
merged 1 commit into from
Dec 5, 2024
Merged

[back] sec: upgrade Django to 4.2.17 from 4.2.16 #2036

merged 1 commit into from
Dec 5, 2024

Conversation

GresilleSiffle
Copy link
Collaborator

@GresilleSiffle GresilleSiffle commented Dec 5, 2024 •
edited
Loading

Description

Fix:

See: https://docs.djangoproject.com/en/4.2/releases/4.2.17/

Checklist

  • I added the related issue(s) id in the related issues section (if any)
    • if not, delete the related issues section
  • I described my changes and my decisions in the PR description
  • I read the development guidelines of the CONTRIBUTING.md
  • The tests pass and have been updated if relevant
  • The code quality check pass

@GresilleSiffle GresilleSiffle added Backend Back-end code of Tournesol Security Will increase the software security labels Dec 5, 2024
@GresilleSiffle GresilleSiffle self-assigned this Dec 5, 2024
@GresilleSiffle GresilleSiffle merged commit 59f57e7 into main Dec 5, 2024
8 checks passed
@GresilleSiffle GresilleSiffle deleted the sec-update_django_to_4.2.17 branch December 5, 2024 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@amatissart amatissart amatissart approved these changes

Assignees

@GresilleSiffle GresilleSiffle

Labels
Backend Back-end code of Tournesol Security Will increase the software security
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@GresilleSiffle @amatissart