4 ms·
Ugh. If the model name includes sem_ver version number, increment the version number when making a new release! Anthropic learned this lesson. Google, Deepseek
by scosman 1y ago
Ugh. If the model name includes sem_ver version number, increment the version number when making a new release!
Anthropic learned this lesson. Google, Deepseek, Kimi, OpenAI and others keep repeating it. This feels like Gemini_2.5_final_FINAL_FINAL_v2.
- rsc 1y agoFWIW, the versions are not semver but they do follow a defined and regular version schema: https://ai.google.dev/gemini-api/docs/models#model-versions https://ai.google.dev/gemini-api/docs/models#model-versions.
- Imustaskforhelp 1y agoI am seeing a lot of demand for something like a semver for AI models. Could thereotically there could be something like a semver that can be autogenerated from that defined and regular version scheme that you shared? Like, Honestly my idea of it is that I could use something like openrouter and then just change the semver without having to worry about these soooo many things as the schema that you shared y'know? A website / tool which can create a semver from this defined scheme and vice versa can be really cool actually :>
- CaptainOfCoit 1y agoI'm not sure if this is a joke or not, but in case it isn't: Semver was mostly created so users of libraries could judge if a new release would break the API interfaces or not, by just looking at the version. So unless the first number changed, you're good to go (in theory, in practice this obviously didn't work as expected). With that in mind, what exactly would semver (or similar) represent for AI models? Setup the proper way, your pipelines should continue working regardless of the model, just that the accuracy or some other metric might change slightly. But there should never be any "breakages" like what semver is supposed to help flag.
- scosman 1y agoModels have changes worthy of semver style major changes. Tokenizer, tool support, tool format, JSON modes, etc. Pipelines absolutely must change when these change. This thread is more about the minor number: not incrementing it when making changes to the internals is painful for dependency tracking. These changes will also break apps (prompts are often tuned to the model).
- qafy 1y ago2.5 isn't the version number, its the model generation. it would only be updated when the underlying model architecture, training, etc are updated. this release is, as the name implies, the same model but likely with hardware optimizations, system prompt, and fine-tuning tweaks applied.
- ComputerGuru 1y agoOk, so if not 2.6 then 2.5.1 :)
- scosman 1y agoIf the weights have changed via training (they have) it’s a new model. This isn’t “hardware optimizations”. It’s additional training/new-weights.