Lock file is pinned to a different registry source
Type URI: https://modeled-information-format.github.io/mif-rs/references/errors/lock-source-mismatch/v1
HTTP status: 409
Exit code: 1
Emitted by: mif-rh (MifRhError::LockSourceMismatch)
Message
Section titled “Message”ontologies.lock.json is pinned to source '{lock_source}', not '{requested_source}' — refusing to evaluate pin safety against a different registry than the one the lock trustsontologies.lock.json’s pinned source differs from the source a read-only
pin-safety check was asked to evaluate against, so the lock’s per-id
version/sha256 pins are not meaningful trust anchors for this source.
Unlike fetch, which legitimately adopts a new source on first use and
re-pins it, a read-only check never mutates the lock, so it fails closed
rather than silently comparing a mismatched source’s registry entries
against pins it never established.
Suggested fix
Section titled “Suggested fix”Unspecified — re-run against the source ontologies.lock.json is actually pinned to, or delete the lock to intentionally re-pin against the new source.