Revert "Bump next from 12.3.1 to 13.5.0 (#642)" #671
Merged
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
This reverts commit e06a0e2.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
rael346
approved these changes
Nov 23, 2023
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 reverts commit e06a0e2.
Hotfix to fix a spiraling staging build.
Details pasted from Slack:
It seems like the combination of the
nextandaxiosupdates broke the prod frontend docker container (can repro if you checkout commit e06a0e2) and build + run the frontend container.Since the build errored on startup (Error: Cannot find module '/app/server.js'), ECS has been trying to restart it continuously for a few days, which will probably add a bit billing-wise (edit: doesn't seem to have made a billing difference, AWS might just not charge for startup time?).
Staging has been up since then only because ECS keeps the old ECR revision running until the new one starts successfully. Therefore, it's been running on an old revision/commit.
I've temporarily fixed the issue by manually redeploying an old commit hash to ECS but this PR should be merged so the issue doesn't resurface the next time someone merges into main (as commits to main cause an automatic staging redeploy)