sbt-version-policy
sbt-version-policy copied to clipboard
scalacenter
Compatibility checks for your dependencies
`sbt-release` has the `setNextVersion` release step which is where we loosly decide what the next version should be. For example, releasing `1.0.0` will set the next version to `1.0.1-SNAPSHOT`. `version`...
Sometimes a stable library in its `0.x` version decides to release a stable `1.x` version since it has a stable API and it wants to communicate with its users. According...
See #119 I think to avoid needing a special SBT configuration I would need to make similar changes in sbt-mima :( But so far this PR enables the following diff...
I noticed that `versionPolicyAssessCompatibility` (added in PR https://github.com/scalacenter/sbt-version-policy/pull/184) **always** reports `None` compatibility for the `aws-parameterstore-lambda` submodule in the project [`play-secret-rotation`](https://github.com/guardian/play-secret-rotation) (configured for `sbt-version-policy` with https://github.com/guardian/play-secret-rotation/pull/416), while all other modules are...
Found via https://github.com/scalacenter/scalafix/issues/1673. When `mimaPreviousArtifacts` is already set by another plugin that happens to run before `SbtVersionPolicyPlugin`, the value gets overriden (in the case of Scalafix, `mimaPreviousArtifacts` is set to...
Before writing this, I noticed #109, which I guess is related. However, this is about getting a more detailed report, both from running MiMa and about dependency bumps. Another difference...
https://github.com/scalacenter/sbt-version-policy/blob/323d01065b08794e3d617b18722d7fb06fa6f67a/sbt-version-policy/src/main/scala/sbtversionpolicy/Compatibility.scala#L63-L85 assumes the module being checked is early-semver as of v2.0.1. It should either support other `versionScheme`s or fail if it's not `early-semver`.
See discussion in #119 Perhaps the API could use Coursier data types, since SBT, Mill, and a lot of other Scala tooling understand them. Perhaps this module would be purely...
I find it convenient to scope the setting for declaring dependency rules to `ThisBuild` so that it is shared across my build. However, this doesn’t work with Scala.js modules, which...
