Skip to content

Upgrade Django to 5.2. Closes #502#579

Merged
regulartim merged 3 commits intodevelopfrom
django_upgrade
Oct 3, 2025
Merged

Upgrade Django to 5.2. Closes #502#579
regulartim merged 3 commits intodevelopfrom
django_upgrade

Conversation

@regulartim
Copy link
Copy Markdown
Collaborator

Description

Upgrades Django to 5.2 and PostgreSQL to 18. An upgrade guide has been already committed to the docs repo:
intelowlproject/docs@0e8a8cf

Related issues

Type of change

Please delete options that are not relevant.

  • Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

  • I have read and understood the rules about how to Contribute to this project.
  • The pull request is for the branch develop.
  • I have added documentation of the new features.
  • Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
  • I have added tests for the feature/bug I solved. All the tests (new and old ones) gave 0 errors.
  • If changes were made to an existing model/serializer/view, the docs were updated and regenerated (check CONTRIBUTE.md).
  • If the GUI has been modified:
    • I have a provided a screenshot of the result in the PR.
    • I have created new frontend tests for the new component or updated existing ones.

Important Rules

  • If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
  • If your changes decrease the overall tests coverage (you will know after the Codecov CI job is done), you should add the required tests to fix the problem
  • Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review. After being reviewed and received a "change request", you should explicitly ask for a review again once you have made the requested changes.

(this requires manual manual intervention when upgrading GreedyBear)
@regulartim regulartim requested a review from mlodic October 3, 2025 08:34
@regulartim regulartim marked this pull request as ready for review October 3, 2025 08:35
@mlodic mlodic linked an issue Oct 3, 2025 that may be closed by this pull request
@regulartim regulartim merged commit d7ad7e4 into develop Oct 3, 2025
5 checks passed
@regulartim regulartim deleted the django_upgrade branch October 3, 2025 09:01
regulartim added a commit that referenced this pull request Oct 3, 2025
* Include mass scanners in advanced API by default. Closes #580 (#581)

* Partly revert "added mass scanner exclusion as default"

This reverts commit f953887.

* adapt tests

* add "tor exit nodes" to default excludes

* add test case for tor exit node inclusion

* add test case for tor exit node inclusion (ii)

* fix syntax

* rename method

* Upgrade Django to 5.2. Closes #502 (#579)

* bump django-rest-email-auth

* bump django to 5.2

* bump postgres to 18
(this requires manual manual intervention when upgrading GreedyBear)

* Link to admin interface for staff users. Closes #529 (#582)

* remove restriction to only show link to superusers

* fix indentation

* bump 2.0.0

* adapt CI
anarghya-12 pushed a commit to anarghya-12/GreedyBear that referenced this pull request Feb 13, 2026
* Include mass scanners in advanced API by default. Closes GreedyBear-Project#580 (GreedyBear-Project#581)

* Partly revert "added mass scanner exclusion as default"

This reverts commit f953887.

* adapt tests

* add "tor exit nodes" to default excludes

* add test case for tor exit node inclusion

* add test case for tor exit node inclusion (ii)

* fix syntax

* rename method

* Upgrade Django to 5.2. Closes GreedyBear-Project#502 (GreedyBear-Project#579)

* bump django-rest-email-auth

* bump django to 5.2

* bump postgres to 18
(this requires manual manual intervention when upgrading GreedyBear)

* Link to admin interface for staff users. Closes GreedyBear-Project#529 (GreedyBear-Project#582)

* remove restriction to only show link to superusers

* fix indentation

* bump 2.0.0

* adapt CI
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.

Support for PostgreSQL 13 ends in November 2025

2 participants