-
Notifications
You must be signed in to change notification settings - Fork 161
Comparing changes
Open a pull request
base repository: Masterminds/semver
base: v3.3.1
head repository: Masterminds/semver
compare: v3.4.0
- 16 commits
- 7 files changed
- 2 contributors
Commits on Feb 10, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 40e0183 - Browse repository at this point
Copy the full SHA 40e0183View commit details
Commits on Jun 18, 2025
-
Configuration menu - View commit details
-
Copy full SHA for c597d50 - Browse repository at this point
Copy the full SHA c597d50View commit details -
Restore detailed errors when failed to parse with NewVersion
When the NewVersion regex was updated to be more accurate, some of the returned errors were lost. Some projects (e.g., Helm) had tests for this and caught the different returned error. This change restores those errors by default but provides a package level opt-out that is more performant. Signed-off-by: Matt Farina <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for f32e01f - Browse repository at this point
Copy the full SHA f32e01fView commit details -
Merge pull request #262 from mattfarina/restore-errors
Restore detailed errors when failed to parse with NewVersion
Configuration menu - View commit details
-
Copy full SHA for 5f491cf - Browse repository at this point
Copy the full SHA 5f491cfView commit details -
updating go version tested with
Signed-off-by: Matt Farina <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 35ee4e7 - Browse repository at this point
Copy the full SHA 35ee4e7View commit details -
Merge pull request #263 from mattfarina/go124
updating go version tested with
Configuration menu - View commit details
-
Copy full SHA for 6fec737 - Browse repository at this point
Copy the full SHA 6fec737View commit details
Commits on Jun 24, 2025
-
Restore the ability to have leading 0's with NewVersion
NewVersion has long been a function that coerces versions into SemVer. StrictNewSemver handles being strict about versions. While leading 0's was restored, this adds an option for package users to force NewVersion to be strict and not accept leading 0's. It does less to coerce a version into a valid one. Signed-off-by: Matt Farina <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 4ed619e - Browse repository at this point
Copy the full SHA 4ed619eView commit details -
Merge pull request #266 from mattfarina/restore-calver
Restore the ability to have leading 0's with NewVersion
Configuration menu - View commit details
-
Copy full SHA for ebda872 - Browse repository at this point
Copy the full SHA ebda872View commit details
Commits on Jun 26, 2025
-
Handle pre-releases on all in an and group
Up to this point, all versions in an and group needed to have a prerelease to be checked with those correctly. This change enables just one item in an and group to have a pre-release and engage it for all items in that and group. This does not work across ORs. For example, `>= 1.2.3 < 2.0.0-beta || > 3` will evaluate prereleases in the group between 1.2.3 and 2.0.0-beta but will not look at prereleases when looking at `>3`. Signed-off-by: Matt Farina <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for abab1c2 - Browse repository at this point
Copy the full SHA abab1c2View commit details -
Merge pull request #267 from mattfarina/fix-259
Handle pre-releases on all in an and group
Configuration menu - View commit details
-
Copy full SHA for 057c901 - Browse repository at this point
Copy the full SHA 057c901View commit details -
Add property to include prereleases
On the Constraints type there is now a property IncludePrerelease. When set, prereleases will be included when checking or validating constraints. This is additive to the existing behavior where a prerelease in a constraint causes the checks to include prereleases. The existing behavior has not changed. Signed-off-by: Matt Farina <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for c374751 - Browse repository at this point
Copy the full SHA c374751View commit details -
Merge pull request #268 from mattfarina/include-prerelease
Add property to include prereleases
Configuration menu - View commit details
-
Copy full SHA for 9760c47 - Browse repository at this point
Copy the full SHA 9760c47View commit details -
Updating the error message handling
Two changes happened: 1. Error messages follow community standards on case 2. Error messages passed in format strings use %w so error handling tools can operate on them. Signed-off-by: Matt Farina <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for a2cd9c2 - Browse repository at this point
Copy the full SHA a2cd9c2View commit details -
Merge pull request #269 from mattfarina/lowercase-error-strings
Updating the error message handling
Configuration menu - View commit details
-
Copy full SHA for dc05094 - Browse repository at this point
Copy the full SHA dc05094View commit details
Commits on Jun 27, 2025
-
Update the release notes and readme for new version
Signed-off-by: Matt Farina <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 69a63e7 - Browse repository at this point
Copy the full SHA 69a63e7View commit details -
Merge pull request #270 from mattfarina/relnotes-3.4.0
Update the release notes and readme for new version
Configuration menu - View commit details
-
Copy full SHA for 61fc460 - Browse repository at this point
Copy the full SHA 61fc460View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.3.1...v3.4.0