Comment by weego
1 day ago
You absolutely cannot consider an LLM production build number something to be pinned against as a static dependency in a product chain, so it's a non-issue.
1 day ago
You absolutely cannot consider an LLM production build number something to be pinned against as a static dependency in a product chain, so it's a non-issue.
Yes you can and you should. Providers have SLAs for when models roll off support and this has been the case for APIs long before LLMs. For example https://platform.claude.com/docs/en/about-claude/model-depre... and https://developers.openai.com/api/docs/deprecations
It's very easy to tell who is not running production applications using these models based on comments like this
Let me give you the benefit of the doubt, can you expand what you run in production?
I'm the founder of a SaaS in the marketing industry with tens of thousands of paying users and we have lots of AI powered workflows where small changes between model versions can make some big differences so whenever we update models we have to thoroughly test them which is why we pin them at specific versions which has been a best practice (and common sense) for the last 3+ years
In the openai api and many other rapid you can pretty trivially pin not only the model but also the specific snapshot you want to use by using the model id for that snapshot. It's not that big a deal and has been available for years