Version Drift

Version drift is the growing gap between the software version a team believes it is running and the version that is actually deployed. It shows up most often where a version reference points not to a fixed commit or artifact but to a moving pointer — an npm dist-tag like `latest`, a container tag like `stable`, or a model alias. Those pointers shift the moment a provider ships a new release, with no change to your own code or config. A security patch can go live upstream while individual machines, CI runners, or developer environments stay on the old build because of caching or staggered rollout, leaving a team convinced a fix is everywhere when it isn't. The problem compounds in AI agent systems, where agents frequently pull packages or launch tools through moving tags on their own, so two runs of the "same" pipeline can silently execute different code with no record of the discrepancy. Version drift becomes visible when debugging sessions produce inconsistent behavior despite an apparently identical build, or when a known bug persists after a patch was supposedly rolled out everywhere. Catching it early pays off directly: shorter root-cause investigations, security sign-offs you can actually trust, and a clear answer to "what build is really running right now." At Context Studios, every audit checks whether version references resolve to a fixed artifact rather than a moving tag before we confirm an environment as patched.