Publish releases with version numbers
Closed this issue · 6 comments
I'm using the LLM libraries from this repo in an app that will soon be available for distribution, and it would be helpful to specify release versions to determine compatibility with new models as they're released and the libraries are updated to run them. Otherwise, older versions of the app might crash or not function properly if they try to run a newer model with an older, incompatible version of the libraries.
So specifically start tagging releases of mlx-swift and mlx-swift-examples?
Yes, that would be helpful. My current workaround is to specify commit hashes for those libraries, but it would be more convenient if they followed semantic versioning conventions.
Actually, when I specify commit hashes for both mlx-swift and mlx-swift-examples, I get this error, which means I can't pin specific dependencies in my app without forking these repos and changing their dependencies:
Failed to resolve dependencies mlx-swift is required using two different revision-based requirements (36d63a1 and main), which is not supported
OK, added 0.12.1 (matching v0.12.1 from mlx) on mlx-swift and added a PR (#80) to adopt that. Once that is in I can tag mlx-swift-examples.
Thanks!