Hotfix release 2025.02.03.01 #5588
Closed
Conversation
This file contains 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
We email people that their subscription is about to expire, then mark them as having received the email. We check whether we have marked someone as having received the email when collecting the list of subscribers to email, which means that we shouldn't use that list when determining whether someone can renew. I've updated it to use a similar check, but to skip the check for `churn_prevention_email_sent_at`.
|
Preview URL 🚀 : https://blurts-server-pr-5588-mgjlpikfea-uk.a.run.app |
flozia
approved these changes
Feb 4, 2025
flozia
approved these changes
Feb 4, 2025
Vinnl
force-pushed
the
release/2025.02.03.01
branch
from
9c187f8 to
eaf716b
Compare
|
Closing this because apparently building the image on non- |
|
Cleanup completed - database 'blurts-server-pr-5588' destroyed, cloud run service 'blurts-server-pr-5588' destroyed |
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.
This is branched off the tag
2025.02.03, with commit 317064f (from #5587) applied on top.When we're ready to deploy, I can tag a new release
2025.02.03.01from this branch so we can deploy that, and after merge it back tomain(should be a no-op after 2025.02.03.01).