[Additive] OpenAI: Value restriction lifted

OpenAI's published API specification now accepts additional values for the VectorStoreExpirationAfter object's anchor field, removing the previously documented value list that restricted it to "last_active_at". The change affects code sending VectorStoreExpirationAfter objects across 4 OpenAI operations, and existing requests continue to work. The update is a relaxation of the schema rather than a breaking change, according to the specification-based report.

What changed A relaxation, not a break. Everything you could send before still works, and more is accepted now. Affects VectorStoreExpirationAfter reachable from 4 operations. the documented value list is gone; more is accepted now Who is affected Code that sends OpenAI's VectorStoreExpirationAfter objects, used by 4 OpenAI operations. Before and after | Where | Before | After | |---|---|---| | VectorStoreExpirationAfter.anchor | "last active at" | absent | Based on OpenAI’s published API specification. How severity is decided https://driftwatch.et/method .