cloudinary_scala
cloudinary_scala copied to clipboard
Do not use snapshot version to publish lib
It is a very bad practive to use snapshot version to maven/sbt publish artifact because you can change lib without updating version and perform bugs in production app user of the artifact.
This has happened to us multiple times. You guys keep changing APIs of previously published version, breaks our builds and sometimes even the production instances.
Why on earth do you publish snapshot versions? Because you are too lazy to push this into a proper repository? No time for doing proper releases?
This issue is almost a year old. Please have at least the decency to tell us why you opted for this braindead release mgmt.