Updating the engine

The Dockerfile starts from builder-www:latest or builder-docs:latest, so every build takes the current engine. But only a new commit builds and rolls: re-running an old pipeline produces an image with the same tag, and a deployment whose image tag has not changed does not restart. When nothing in the content needs changing, make an empty commit and say why:

git commit --allow-empty -m "Rebuild on the current engine: new header layout"
git push

To move deliberately instead, pin a version: builder-www:0.24.4. Versions are the engine’s release numbers; latest always points at the newest.