Bump django-environ from 0.11.2 to 0.12.0

[dependabot]

Bumps django-environ from 0.11.2 to 0.12.0.

Changelog

Sourced from django-environ's changelog.

v0.12.0_ - 8-November-2024

Fixed +++++

• Include prefix in the ImproperlyConfigured error message [#513](https://github.com/joke2k/django-environ/issues/513) <https://github.com/joke2k/django-environ/issues/513>_.

Added +++++

• Add support for Python 3.12 and 3.13 [#538](https://github.com/joke2k/django-environ/issues/538) <https://github.com/joke2k/django-environ/issues/538>_.
• Add support for Django 5.1 [#535](https://github.com/joke2k/django-environ/issues/535) <https://github.com/joke2k/django-environ/issues/535>_.
• Add support for Django CockroachDB driver [#509](https://github.com/joke2k/django-environ/issues/509) <https://github.com/joke2k/django-environ/issues/509>_.
• Add support for Django Channels [#266](https://github.com/joke2k/django-environ/issues/266) <https://github.com/joke2k/django-environ/issues/266>_.

Changed +++++++

• Disabled inline comments handling by default due to potential side effects. While the feature itself is useful, the project's philosophy dictates that it should not be enabled by default for all users [#499](https://github.com/joke2k/django-environ/issues/499) <https://github.com/joke2k/django-environ/issues/499>_.

Removed +++++++

• Removed support of Python 3.6, 3.7 and 3.8 [#538](https://github.com/joke2k/django-environ/issues/538) <https://github.com/joke2k/django-environ/issues/538>_.
• Removed support of Django 1.x. [#538](https://github.com/joke2k/django-environ/issues/538) <https://github.com/joke2k/django-environ/issues/538>_.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dryrunsecurity]

DryRun Security Summary

The code change updates the django-environ package from version 0.11.2 to 0.12.0 in the requirements.txt file, representing a routine dependency update with no significant security implications.

Expand for full summary

Summary:

The provided code change represents an update to the requirements.txt file, which is a file used to manage the dependencies of a Python-based application, in this case, the DefectDojo project. The key change is the update of the django-environ package from version 0.11.2 to 0.12.0.

From an application security perspective, this update is not particularly noteworthy. The django-environ package is a utility library that allows for the management of environment variables in Django applications, which is a common and recommended practice. Version upgrades of this type are typically non-breaking and do not introduce significant security implications. However, it's always a good practice to review the changelog or release notes for any dependency updates to ensure there are no known security vulnerabilities or breaking changes that could impact the application. Additionally, it's recommended to keep all dependencies up-to-date to benefit from the latest bug fixes and security patches.

Overall, this code change appears to be a routine dependency update and does not raise any immediate security concerns. The review should focus on ensuring that the updated dependencies do not introduce any regressions or conflicts with the rest of the application.

Files Changed:

• requirements.txt: This file has been updated to include the new version of the django-environ package, from 0.11.2 to 0.12.0. This is a common and recommended practice for managing dependencies in a Python-based application.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

View PR in the DryRun Dashboard.

[mtesauro]

Approved