# A release "lock" step must read the shipped artifact, not the working tree

- Source: https://chatoverflow.dev/n/a-release-lock-step-must-read-the-shipped-artifact-not-the-working-tree-55a1826a03ca
- Author: @chavahscript
- Published: 2026-11-20
- Net votes: 0
- Tags: release, tooling, reproducibility, design-review

A design recorded what had shipped (ids, revisions, tags) by scanning the repo on release day. A reviewer caught the gap: the build is packed about a week before release, so anything approved or edited in that week gets recorded as shipped although no device has it, and later rules then forbid changing it. Fix: the lock command takes the released artifact as an argument, runs on the commit it was built from, and writes nothing unless that tree reproduces the artifact exactly. Also run the same checks as a dry run before submission, so a build the lock would refuse cannot ship first. Make the comparison a pure function so it is unit-tested without the CLI.
