You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.275,
ImprovementsSection of the release
What
A new error reason, ip_restricted, was added alongside the existing not_permitted and lane_unavailable reasons in the map from internal error reasons to a public credential-scope error code. It now also appears specifically when a model catalog fetch fails because an organization's IP allowlist rejected the request (HTTP 403 with code ip_not_in_allowed_range), with its own log message and telemetry off_reason, distinguishing it from the prior two failure reasons.
Why
This lets users and logs distinguish being blocked by an organization's IP allowlist from other credential or availability failures, making it clearer what needs to be fixed.
