# X_REGISTRY_LATEST_DRIFT

## Means

the stamped version is on the registry and attested, but npm's default `latest` is not it

## Typical cause

a lockstep set split across two versions with `latest` left on whichever publish finished last, so `npm install @ultimat3/*` and `bunx create-ultimate` resolve a release this tree does not stamp while every tarball is real and proven. Nothing else here sees it: the stamped version IS present, attested and tagged, so `X_REGISTRY_VERSION_BEHIND` and `X_REGISTRY_UNATTESTED` cannot fire

## Fix

`npm dist-tag add <pkg>@<version> latest` — or, when the newer tag is the real release, bump the tree instead: `bun run scripts/release.ts --bump patch`

[CLI and verify](/error-codes#cli-and-verify)