Fix version-number confusion - skip straight to v1.0.0! #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This library has had some version-number confusion:
version.sbt
version.sbt
(git
tag)version.sbt
(and didn't get agit
tag)version.sbt
This repo adopted
gha-scala-library-release-workflow
with #47 and v0.4.5 in 2024/07/26 - before that the release procedure was much more manual & error-prone!To get past the confusion, it's best to jump to a version number higher than 0.6.0 - and as this library, like all libraries that use
gha-scala-library-release-workflow
, is usingearly-semver
, it makes sense to move past 0.y.z as a version number - underearly-semver
:To avoid the complication of trying to understand that, better to just get to v1 and above!