Adds dismissal of AddOnEvents, bumps Python and fixes collectstatic#436
Merged
Conversation
Hide addon events, merge commits that are on master onto staging.
eyeseast
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes Support deleting or hiding add-on events #428
The default view will return all AddOnEvents. The front-end can pass dismissed=False to filter out the dismissed events or dismissed=True to show the dismissed events to maintain backwards compatibility.
Adds invoke tasks to bring the local dev containers up and down, similar to Accounts and Requests.
Bumps Python to 3.12 on Heroku. This was meant to be added to the Django 5 branch. The local dockerfile uses 3.12 already as does lambda. The testing apparatuses all use 3.12 as well. I just forgot to update this file.
I noticed both on staging and production when you go to an API endpoint the "Filters" button does nothing. When I inspected the network requests on that page for staging, I saw a 403 for version 3.7.1 of jQuery. I inspected the bucket where these files were actually supposed to be hosted and the last pushes were in 2021. jquery-3.5.1.min.js — dated 2021
This wasn't a problem in the Django 4 upgrade because it maintained backwards compatibility, but was a breaking change in 5 that wasn't caught.
STATICFILES_STORAGE was deprecated in 4.2:
https://docs.djangoproject.com/en/4.2/ref/settings/#std-setting-STATICFILES_STORAGE
and completely removed in 5.1 and swapped with STORAGES (which was new in Django 4.2)
https://docs.djangoproject.com/en/4.2/ref/settings/#std-setting-STORAGES