All writing
Why Production Can Stay Old Even When Deployment Is Green
A successful deployment does not prove that the expected build is what the custom domain is serving.
DEC-RELEASESeparate release, rescue and operations needs.
CI is green. The hosting dashboard says success. The user still sees the old product.
Do not rewrite the component yet.
I check the release chain in order: correct repository, branch, deployed commit, build artifact, production-branch configuration, custom-domain binding, cache, service worker and finally the build identity served by the production URL.
“Deployment succeeded” and “the expected version is live” are different claims.
A release gate closes only when the second one is verified.
Rescue & Ownership
Production rescue through root-cause diagnosis, release reality and operational ownership instead of repeated symptom patches.