Skip to content

Upgrade to Django 4.2 #160

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

Merged
merged 2 commits into from
Jun 4, 2024
Merged

Conversation

davidfischer
Copy link
Member

@davidfischer davidfischer commented Jun 4, 2024

  • Stop using pytz and use zoneinfo
  • Small changes to storages configuration
  • USE_L10N is deprecated (default on) and will be always on starting with Django 5

https://docs.djangoproject.com/en/4.2/releases/4.2/

Fixes #154

- Stop using pytz and use zoneinfo
- Small changes to storages configuration
- USE_L10N is deprecated (default on) and will be
  always on starting with Django 5
@davidfischer davidfischer requested a review from a team June 4, 2024 00:51
@@ -40,7 +40,7 @@ COPY . /code/
RUN --mount=type=cache,target=/root/.npm npm install
RUN npm run build

RUN python manage.py collectstatic --noinput
RUN python manage.py collectstatic --noinput --clear
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is minor but fixes a warning when building the container locally. Since the static directory won't exist when GitHub Actions is building it for deployment, this only helps dev.

Copy link
Contributor

@Jer-Pha Jer-Pha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • All discussed changes from Upgrade to Django 4.2 #154 are addressed
  • All third-party apps and middleware are compatible w/ Django 4.2
  • All doc URLs are valid (manually checked)
  • TZ changes look good

@davidfischer davidfischer merged commit 8423453 into main Jun 4, 2024
1 check passed
@davidfischer davidfischer deleted the davidfischer/upgrade-to-django-42 branch June 4, 2024 16:37
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.

Upgrade to Django 4.2
2 participants