The bump-version action should be changed to read the current version from git tags. This will pave the way for it to become more agnostic for non-JS projects as well as allow for continuous releases to be versioned without commits to package.json (as GitHub releases automatically create tags)
Acceptance Criteria
AC1
Given a list of semver git tags off the main branch
When bump-version is run
Then the latest (date descending? or semver descending?) git tag is used to bump the next version
Notes
npm version from-git --no-git-tag-version can be used to sync package.json with the latest git tag without creating a commit or tag.
git tag --sort=-version:refname gets the latest git tag for all git tags, including those detached. This is useful for the github releases that'll be created but not have the version bump commit pushed back to any branc.
The
bump-versionaction should be changed to read the current version from git tags. This will pave the way for it to become more agnostic for non-JS projects as well as allow for continuous releases to be versioned without commits topackage.json(as GitHub releases automatically create tags)Acceptance Criteria
AC1
Given a list of semver git tags off the main branch When bump-version is run Then the latest (date descending? or semver descending?) git tag is used to bump the next version
Notes
npm version from-git --no-git-tag-versioncan be used to syncpackage.jsonwith the latest git tag without creating a commit or tag.git tag --sort=-version:refnamegets the latest git tag for all git tags, including those detached. This is useful for the github releases that'll be created but not have the version bump commit pushed back to any branc.