Releases: isomarcte/sbt-version-scheme-enforcer
v2.1.0.3
This release is not breaking in anyway.
Overview
This is a minor bug fix release. Certain version strings containing + characters were not being properly parsed into numeric string values. This mostly comes into play with sbt-dynver. This has been fixed and should be invisible to most users.
v2.1.0.2
v2.1.0.1
This release contains no binary breaking changes or other changes to the visible binary API.
Overview
This release fixes a bug where running versionSchemeEnforcerCheck would fail if versionSchemeEnforcerPreviousVersion was not defined, even if versionSchemeEnforcerInitialVersion is set. The correct behavior is to only fail during the versionSchemeEnforcerCheck if both the versionSchemeEnforcerInitialVersion and versionSchemeEnforcerPreviousVersion are unset.
v2.1.0.0
This release is non-binary breaking. The major version bump is due to a deprecation as required by PVP.
Changes
- The key
versionSchemeEnforcerIntialVersionwas deprecated and replaced withversionSchemeEnforcerInitialVersiondue to a spelling error in the name of the key (Intial -> Initial). No behavior changes were made.
v2.0.0.1
Overview
This release is complete binary compatible with 2.0.0.0.
This is a bug-fix release. A println used for debugging a git commend as accidentally (and embarrassingly) committed. This release removes this. Otherwise no other user facing changes have been made.
v2.0.0.0
Overview
This release provides some new features, updates dependencies, and adds some internal changes to support more Version Control Systems (VCS) in the future.
None of sbt-version-scheme-enforcer's Plugin API nor it's own binary API was broken. This is a major version bump because sbt-mima-plugin was updated from 0.8.1 to 0.9.0. As that project uses early-semver, this indicates a potentially breaking transitive dependency for our users. That said, I would be very surprised if anyone was affected by this change in any way.
New Features
- Added new Setting
versionSchemeEnforcerPreviousTagFilter- This setting permits filtering out certain VCS tags when using VCS tags to automatically detect the previous version. A common use case for this is filtering out milestone releases so that binary changes between two milestones can be ignored, but binary changes against the most recent non-milestone release can still be considered. See the FAQ for more information.
TagFiltersprovides common filters for users.
Dependency Changes
sbt-mima-plugin0.8.1->0.9.0- Breaking
coursier-versions0.3.0->0.3.1- New symbols, not binary breaking
v1.0.0.1
This release contains a single bug fix. No visible behavioral changes were made and there were no changes to binary compatibility.
Bug Fixes
This release fixes a bug in the build.sbt definition of this project where the SBT specific dependencies were not listed as Provided. This project uses https://github.com/cb372/sbt-explicit-dependencies to ensure that we explicitly depend on (rather than transitively depend on) all the dependencies which provide symbols we explicitly use. The SBT dependencies are provided (https://maven.apache.org/pom.html#pom-relationships) by SBT itself though, so we should not list them as explicit.
By listing them as explicit, an issue arose that SBT 1.5.1 was evicting its own dependencies in favor of this plugins dependencies. This behavior seems a bit counter intuitive and I'm honestly not sure if it is intended, however in any case listing the dependencies as provided prevents this issue.
v1.0.0.0
This release updates to build against sbt 1.5.0.
Internally, it is backwards compatible with 0.3.0.0 and 0.2.0.0.
v0.2.0.0
Add versionSchemeEnforcerIntialVersion to allow for specifying a version after which the version scheme is enforced.
v0.1.0.0
- Allow versionSchemeEnforcerPreviousVersion To Be Empty
- Permit versionSchemeEnforcerPreviousVersion to be empty to signal that there is no previous release