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

fix: use STORAGES instead of STATICFILES_STORAGE #827

Merged
merged 1 commit into from
Sep 12, 2024

Conversation

MatMoore
Copy link
Contributor

@MatMoore MatMoore commented Sep 12, 2024

The latter is deprecated since django 4.2
https://docs.djangoproject.com/en/5.0/ref/settings/#staticfiles-storage

And then it was dropped in 5.1
https://docs.djangoproject.com/en/5.1/releases/5.1/#features-removed-in-5-1

This broke our cache busting URLs, added in #331

@MatMoore MatMoore changed the title refactor: use STORAGES instead of STATICFILES_STORAGE fix: use STORAGES instead of STATICFILES_STORAGE Sep 12, 2024
@MatMoore MatMoore marked this pull request as ready for review September 12, 2024 13:37
@MatMoore MatMoore requested a review from a team as a code owner September 12, 2024 13:38
@MatMoore MatMoore merged commit 88c9e64 into main Sep 12, 2024
21 checks passed
@MatMoore MatMoore deleted the fmd-774-cache-busting branch September 12, 2024 14:04
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