Model aliases pointing at models you lack access to are now correctly rejected.
What's wrong with this entry?
A model name that maps onto an unentitled API model via a configured override is now correctly recognised as unentitled, instead of passing the check because the alias itself was not in the set.
- in addition to the direct set lookup, the predicate walks the configured model overrides from settings and from the cached client data
- a match is reported when any override maps the name onto an unentitled API model
modelOverrides
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Search field in the model picker
Both mention model
-
v2.1.236
Cancellable waits when
/modeltalks to a cloud sessionBoth mention model
-
v2.1.238
Model and effort switch warning now checks whether the cache is actually warm
Both mention model