# X_REGISTRY_VERSION_BEHIND

## Means

the registry holds the package but not the version this tree stamps

## Typical cause

the release that should have published it did not reach it — an aborted run leaves every package after the failure behind

## Fix

`gh workflow run release.yml --ref v<version> -f version=<version>`; when that aborts `EPUBLISHCONFLICT` on a sibling already at the version, `npm publish -w <pkg> --access public --provenance=false`

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