As @c-po pointed out, we've been having quite a few less-than-pleasant situations with releases appearing on the vyos.net/get/snapshots page and then disappearing from it.
In all cases, the situation was like this: a script published an image it wasn't supposed to publish (either at all or yet) and I had to remove it from the page by hand.

This is confusing for the users. It's also inconvenient for the maintainers not to have easy access to the links to the latest pre-release snapshot though.

I suggest the following solution:

• Create a separate "production" branch in the community.vyos.net repository. Only deploys from that branch will go to https://vyos.net
• Create a separate staging.vyos.net domain.
• Create a separate "staging" build profile that will inject a prominent warning in every page about it being a preview version only, so that no one confuses it with the "real" website. Set the main branch workflow to deploy to staging.vyos.net
• Exclude the staging.vyos.net website from search engine indexing and everything we can exclude it from.

Then we can safely have any bugs in the website build scripts. When we are happy with the staging website, we will merge the main branch into "production" to trigger a production deploy.

Thoughts?