Deploy web app less often to reduce cache invalidation#2762
Merged
brandonpayton merged 2 commits intotrunkfrom Oct 9, 2025
Merged
Deploy web app less often to reduce cache invalidation#2762brandonpayton merged 2 commits intotrunkfrom
brandonpayton merged 2 commits intotrunkfrom
Conversation
adamziel
reviewed
Oct 9, 2025
Member
Author
|
Thanks, @adamziel. I'll go ahead and merge this because there is actually no reason to wait for CI AFAICT. |
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
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.
Motivation for the change, related issues
@adamziel mentioned:
This seems like a good idea to me. The workflow for updating major and beta WP versions already triggers a deploy if there are changes. And if we need a deploy for any other reason, we can start one manually.
Implementation details
This changes the web app deployment schedule to 1100 UTC on Tuesday. This way, we avoid creating sudden changes at the beginning of everyone's week but have plenty of time to address any issues before the end of the week.
Testing Instructions (or ideally a Blueprint)