Describe the bug
The service suffered a prolonged outage recently (2024-08-10 to 2024-08-12), and during recovery from that outage, a non-functioning version of this application was deployed.
Ideally we would have simply rolled back to a previous version; however, due to a loss of container images during a parallel, opportunistic maintenance upgrade, those images were not available.
Building from a previous known-good commit (upgrading to use yarn v4, #250) continued to produce a non-functional output, and so to restore service, we've rolled back one step further.
This means that we have dropped some legitimate dependency updates. We want to restore those, and then to redeploy an updated version of the application.
To Reproduce
N/A
Expected behavior
Dependency updates from 548ca3ed93c8761ce9766ecdaa0b265d64902bed should be restored to the main branch.
Tests should pass when running make tests.
Building the application using make build should produce a container image that hosts a functional self-contained version of the application.
Describe the bug The service suffered a prolonged outage recently (2024-08-10 to 2024-08-12), and during recovery from that outage, a non-functioning version of this application was deployed.
Ideally we would have simply rolled back to a previous version; however, due to a loss of container images during a parallel, opportunistic maintenance upgrade, those images were not available.
Building from a previous known-good commit (upgrading to use
yarnv4, #250) continued to produce a non-functional output, and so to restore service, we've rolled back one step further.This means that we have dropped some legitimate dependency updates. We want to restore those, and then to redeploy an updated version of the application.
To Reproduce N/A
Expected behavior
mainbranch.make tests.make buildshould produce a container image that hosts a functional self-contained version of the application.Screenshots N/A