{"version":"2.1.273","anchor":"firstparty-catalog-check-no-longer-requires-matching-release","canonical_anchor":"firstparty-catalog-check-no-longer-requires-matching-release","heading":"firstParty catalog check no longer requires matching release","tier":"internal","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/firstparty-catalog-check-no-longer-requires-matching-release","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### firstParty catalog check no longer requires matching release\n\nModel-catalog readiness check no longer requires the release to match\n\n**Unclear.** The finding doesn't say why the release-matching requirement was removed or what effect this has in practice.\n\n**What**\n\nA check for whether the model catalog is from Anthropic itself (\"first party\") used to also require that the catalog's release matched a specific expected release. That release-matching requirement was removed, so now only the first-party flag is checked.\n\n**Why**\n\nThis loosens the readiness check for the first-party model catalog, meaning it can now be considered ready without also matching a specific release, though the finding doesn't say what problem this fixes.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}