Website updates with a new patch release before container images are built

[danderson]

Is this a bug report or a feature request?:

bug

What happened:

Website is currently pinned to a minor version branch, e.g. v0.3. This means that as soon as I push the tag for a new patch version, the website updates to that patched version. Notably, it tells people to apply manifests that use the new patch version in manifests... But CircleCI only starts building the images when I push, so for a 5-30min window after the push, we're advertising manifests that will crashloop with ImagePullError.

What you expected to happen:

Website should always point to manifests that work.

[danderson]

Hrm, no obviously good way to make this happen. Netlify doesn't support making the main deploy be from a tag, so as soon as I push the updates on the v0.X branch, the website updates.

I think the next best thing is: create a live-website branch, which netlify always deploys as the main site. Then, on each release, after pushing the v0.X branch and letting CircleCI build appropriate images, do a git branch -f live-website v0.X and repush the branch ref to trigger the website deploy.