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.

Sign up for GitHub

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

Jump to bottom

Migrate to Django 4.2+ #71

Closed
sebastienbarbier opened this issue Apr 20, 2023 · 0 comments
Closed

Migrate to Django 4.2+ #71

sebastienbarbier opened this issue Apr 20, 2023 · 0 comments
Assignees
@sebastienbarbier
Milestone
v1.5.0

Comments

@sebastienbarbier
Copy link
Owner

sebastienbarbier commented Apr 20, 2023 •
edited
Loading

We are currently staying at 4.1.x to maintain compatibility with PostgreSQL 11.
This ticket is about migrating all dependencies to django 4.2+ and solve issues with postgreSQL 11.
Main reason to keep PostgreSQL 11 is to keep using prod db from hosting provider.
Need to migrate prod to unlock this.

Related to #67
@sebastienbarbier sebastienbarbier added this to the v1.5.0 milestone Nov 16, 2023
@sebastienbarbier sebastienbarbier self-assigned this Nov 16, 2023
sebastienbarbier added a commit that referenced this issue Nov 27, 2023
@sebastienbarbier
Migrate to Django 4.2+
44724a7 
Fix #71
@sebastienbarbier sebastienbarbier mentioned this issue Jan 2, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sebastienbarbier sebastienbarbier

Labels
None yet
Projects
None yet
Milestone
v1.5.0
Development

No branches or pull requests
1 participant
@sebastienbarbier