I use semantic-release with prerelease branches for infrastructure, but I’m not sure how to apply it to an application container. I want to test an image in dev and then promote that exact image through testing and production without rebuilding it.
Should the stable version be created before dev testing or only after a candidate is validated? How do you handle fixes and new changes arriving on the main branch?
Zavelo-3h:
So newer commits on main wouldn’t change the candidate already being tested?
6q+gaugecradle_318:
Right. Record the candidate’s commit and digest when you select it. New merges can produce other images, but they don’t replace that candidate unless you explicitly select a new one.