The model behind your API name can change while you sleep.
DeepSeek just shipped V4.1-Flash-1017. They say it is faster, finishes tasks quicker and gives shorter answers than the last version, so better quality and lower cost at the same time. Before the launch, the new id showed up in the API for a short time, and testers noticed the general deepseek-flash endpoint already giving shorter, clearer answers.
Good news, mostly. But shorter outputs are also a change in behavior. If your agent parses the answer, expects a certain format, or your evals were tuned on the old version, a quiet update can break things that worked yesterday.
The safer way: pin the dated model id in production, not the general alias. Put the new version behind the same load balancer, run it on real tasks, compare cost per finished task, then switch.
Do you pin model versions in production, or ride the latest alias?