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.

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

Upgrade django to 3.2 #329

Merged
merged 2 commits into from
Sep 27, 2021
Merged

Upgrade django to 3.2 #329

merged 2 commits into from
Sep 27, 2021

Conversation

njbooher
Copy link
Contributor

I've been running with django 3.2 for about a month now and haven't noticed any issues.

Django 3.2 is designated as a long-term support release. It will receive security updates for at least three years after April 6, 2021.

I hereby agree to licence this and any previous contributions under
the terms of the GNU General Public License version 3 as published by
the Free Software Foundation

I have read the CONTRIBUTING.rst file and understand that
TravisCI will be used to confirm the tests and flake8 style
checks pass with these changes.

I am happy be thanked by name in the CONTRIB.rst files,
and have added myself to the file as part of this pull request.
(This acknowledgement is optional. Note we list the names sorted alphabetically.)

@sonarcloud
Copy link

sonarcloud bot commented Sep 27, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@azneto azneto merged commit ffddba8 into lmb-embrapa:master Sep 27, 2021
@njbooher njbooher deleted the upgrade-django branch September 27, 2021 17:26
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.

2 participants