Quick-start tests were added to make sure the "quick start" instructions continue to work, but have proven themselves to be an effective end-to-end integration test.

The quick-start instructions actually just use the latest container versions (i.e. not the latest code). The quick-start tests therefore do their job, but this means the next time someone builds a new container, they have to sort out all the errors from changes made since the last container build.

Solution:

• Run the existing quick-start tests after the release build.
• Add a new "e2e-tests" in the current PR workflow, which does something similar, but with the most recent build of the code.