chore(deps): Upgrade the version of semver package from v1 to v3 #625
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.
Reason for the upgrade
I attempted to use the
semver
update strategy with thex-0
constraint.x-0
signifies any tags that adhere to semantic versioning, whether or not they have prerelease tags.However, the constraint wasn't considering tags with prerelease versions as valid tags.
There was a fix1 in
Masterminds/semver
package, whichargocd-image-updater
uses for semver checks. This fix was included in the v3.2.0 release2 ofMasterminds/semver
and the lastest release isv3.2.1
.Therefore I have upgraded the version of
Masterminds/semver
package from v1 .5.0to v3.2.1.Testing
I have verified that the
x-0
constraint correctly handles prerelease tags by the following test code.The test code includes multiple test cases to cover various scenarios.
Details
Footnotes
https://github.com/Masterminds/semver/pull/176 ↩
https://github.com/Masterminds/semver/releases/tag/v3.2.0 ↩