How do you prove production runs the intended commit?
Build the release artifact from the exact commit and record its identifier and main JavaScript hash in a release marker. Read the live marker and bundle and compare them with the reviewed artifact.
How to check it
- Commit the intended changes before building.
- Verify the artifact targets the correct account, Worker or project.
- After release, inspect the marker, bundle and critical flows on the real domain.
Concrete example
Example: a CLI can report “success” while the domain still serves an old bundle. Matching the marker’s commit and downloaded SHA256 identifies which source version is actually live.
Avoid a false conclusion
A matching commit does not prove product behavior. Login, forms, article details and mobile presentation still require real checks.
Reference
VCT Editorial