v0.5.0

v0.5.0 - 2026-08-22

Changed

• env and envFrom are laid over the environment a target already carries rather than replacing it. Terraform declares the environment and the deploy config refines it, so listing one variable sets one variable instead of deleting every other one — which also removes the need for a mode: a config that sets nothing merges nothing, and that is the image-only deploy. The order is what Terraform declares, then envFrom, then env, then strategy.env for the side being staged, then EVOLVE_DEPLOY_SIDE. The trade is that the config can no longer remove a variable; removal belongs where the declaration is. --allow-env-removal stays, because a variable can still disappear when Terraform stops declaring one a running target has, and the release that carries that through is worth confirming — but it can no longer fire because someone listed one variable and meant to keep thirty.

Fixed

• A blue-green revision is staged from the container app's own template rather than from the serving revision's, so a probe, a cpu change or an environment variable Terraform declares reaches the next release instead of being staged over every time — previously such a change created a revision with no traffic and was reverted rather than delayed. The serving revision is still where the running version and the environment diff are read from, because with two live revisions the app's template is whichever was created last, which after a failed gate is the attempt that was abandoned; comparing against that would report the retry as already up to date.