Systematize version numbers for Auto DevOps apps
Package managers and released apps generally have a concept of a version number. We should formalize a way to manage these within GitLab, at least for Auto DevOps.
I'm not sure what this would look like. With npm
, for example, you generally bump the version number in package.json
as part of your release process. Since the release step would be controlled by a CI/CD pipeline, how could we automate and enforce that?
Should we bump the version number on every commit into master
? Should CI/CD commit the version change and silent push it back to master
?
Should we just leave this all up to the user and rely on tags to convey version numbers?
Should we have an explicit release command that changes the version number, sets tags, and creates artifacts?