Version pinning fixes a deployed model or tool to a specified version, so updates happen by choice rather than automatically. It makes changes reviewable and helps prevent an untested update from silently changing system behavior or capabilities. section 7.3.5 section 4.8.4
Apply pinning as an operational control:
- For a model-provider contract, require the right to pin a specific version and advance notice of updates. Set the provider’s post-deprecation support period to match the time needed to re-validate a replacement; six to twelve months is suggested. section 7.3.5
- For approved agent tools, record the specific version and prevent unreviewed upgrades. Docker’s MCP Catalog supports container-version pinning, while its CI pipeline validates commit hashes. section 4.8.4
Why silent model updates matter
A reported GPT-4 coding-task accuracy score fell from 84% in March 2023 to 51% in June, alongside weaker instruction-following. Pinning lets a deployment team choose when to upgrade and re-validate instead of absorbing such a change automatically. section 7.3.5

