for production LLM API usage, how do you handle model deprecations and changes? pin versions, watch changelogs manually, or something else?
if you're running things in production on LLM APIs (gemini, qwen, openai, kimi, etc.) how do you actually handle model deprecations and changes? say a model you're calling gets retired, or worse, an alias like a "latest" model name just silently repoints to newer snapshot with zero warning, no changelog entry, nothing.
do you manually check each provider's deprecation page, pin specific dated model versions and never touch them, set up some kind of alerting, or mostly just not worry about it until something breaks in prod?
I'm asking because I put together a small experiment that tracks deprecation dates and these "rolling alias" changes across a handful of providers, pulled straight from each vendor's own docs.
before i spend more time on this, trying to understand whether this is an actual pain point people run into, or whether most people just pin a version and move on and it's a non-issue in practice.