This repository has been archived by the owner on Aug 16, 2024. It is now read-only.
Hotfix for upstream dependency's incompatibility with Django 4.1 #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to miracle2k/django-assets#102 (and the fact that we don't really have a way of migrating down when deploying), this is a hotfix that should still allow the
manage.py assets build
command to run.To test locally, run
just build
thenjust manage assets build
.I've changed the post-compile script so that if any step fails, the whole build fails.
I've also added some CI/CD steps to check that assets can still be built.