-
Notifications
You must be signed in to change notification settings - Fork 12
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
postgres 16/python 3.12 #858
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #858 +/- ##
=======================================
Coverage 77.81% 77.81%
=======================================
Files 28 28
Lines 568 568
=======================================
Hits 442 442
Misses 126 126 ☔ View full report in Codecov by Sentry. |
Pillow = "==10.3.0" | ||
Markdown = "==3.3.7" | ||
feedparser = "==6.0.11" | ||
pytz = "==2024.1" | ||
urllib3 = "<3.0.0" | ||
pre-commit = "*" | ||
django = "==4.2.15" | ||
zipp = "*" | ||
certifi = "*" |
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.
Wow. Pipenv makes it really hard to upgrade only one package in the lockfile these days
ValueError: The flag --selective-upgrade flag has been removed
ValueError: The flag --keep-outdated flag has been removed
--lock-only
exists, but the doesn't do what it says it will ( Why --lock-only flag logic removed? pypa/pipenv#6131 )
Question: How can I check this on dev? |
- pipenv verify: ensure lockfile is up to date with Pipfile - django system checks - fail fast on ruff errors - djhtml
Don't think any of the 1.x --> 2.x changes affect this project
ecca8b2
to
a3446a5
Compare
OK, so I tested a deploy (I've now reverted that commit). Interestingly, this application seems to only have production and staging. There's a "Dev - Website - DC" AWS account, but it doesn't seem to have anything in it and the Lines 145 to 151 in 5129aac
so anyway I've checked it on stage.DC .
Other things RDS This application lives on an RDS instance which is shared with some other things. Namely
so we have to be in a position where we want to migrate all of those before we upgrade it. Might be useful to catch up on that tomorrow Safety CI Currently, Safety CI is failing because there is a RCE in setuptools <70 GHSA-cx63-2mw6-8hw5 but dc_django_utils is pinning us to Aside from that I think this one is ready for review though. I reckon it is worth reviewing what is here accepting that the build is failing and it is not merge-able until we fix or ignore that safety error. |
This PR looks like it is changing a lot of files but if you ignore the formatting changes in
it is not too bad.