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

postgres 16/python 3.12 #858

Merged
merged 15 commits into from
Aug 23, 2024
Merged

postgres 16/python 3.12 #858

merged 15 commits into from
Aug 23, 2024

Conversation

chris48s
Copy link
Member

@chris48s chris48s commented Aug 14, 2024

This PR looks like it is changing a lot of files but if you ignore the formatting changes in

it is not too bad.

Copy link

codecov bot commented Aug 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.81%. Comparing base (5129aac) to head (06ec515).
Report is 16 commits behind head on master.

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.
📢 Have feedback on the report? Share it here.

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 = "*"
Copy link
Member Author

@chris48s chris48s Aug 14, 2024

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

@chris48s
Copy link
Member Author

Question: How can I check this on dev?

@chris48s chris48s marked this pull request as draft August 14, 2024 14:31
- 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
@chris48s chris48s changed the title WIP postgres 16/python 3.12 postgres 16/python 3.12 Aug 20, 2024
@chris48s
Copy link
Member Author

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 development branch triggers a deploy to staging

- sam_deploy:
name: sam_deploy_staging
dc-environment: staging
requires:
- sam_build
context: [ deployment-staging-dc-website, slack-secrets ]
filters: { branches: { only: [ main, master, development ] } }

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

  • aggregator-api-production
  • dc-website-production
  • listmonk
  • wcivf_feedback_production

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 setuptools==69.2.0. https://github.com/DemocracyClub/dc_django_utils/blob/43ec52d2846b1b28cfaabd036841456c5f9a4466/pyproject.toml#L13 So that requires some cross-repo work to get the build passing and unblock this.

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.

@chris48s chris48s marked this pull request as ready for review August 20, 2024 12:49
@chris48s chris48s merged commit b474a68 into master Aug 23, 2024
3 checks passed
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