Sbt Release Versions Save

Breaking Change: Prerelease version increments

Prior to sbt-release 1.4.0, if a prerelease version (for example 1.0.0-RC1) is incremented, the prerelease part RC1 is dropped, so 1.0.0-RC1 was incremented to 1.0.0. By default, sbt-release 1.4.0 increments prerelease versions by default, if it ends in a number. In other words, 1.0.0-RC1 is incremented to 1.0.0-RC2.

To restore the previous behavior, you can set the following setting:

releaseVersionBump := sbtrelease.Version.Bump.NextStable

This was contributed by @Andrapyre in https://github.com/sbt/sbt-release/pull/397

Updates

• Update specs2-core to 4.20.4 by @scala-steward-bot in https://github.com/sbt/sbt-release/pull/399

Full Changelog: https://github.com/sbt/sbt-release/compare/v1.3.0...v1.4.0

• #193 The checkSnapshotDependencies release step now has enabledCrossBuild enabled by default.
• #185 Adds a default-tag-exists-answer option to the release command to customise the default response to a tag already existing in the tagRelease release step.
• #194 Makes releaseVersion, releaseNextVersion, and releaseVersionBump task keys instead of setting keys.

v1.0.4...v1.0.5

• #29 The release task automatically runs a cross release build depending on whether crossScalaVersions contains a scala version other than the one defined by the scalaVersion setting key.
• #46 Added a setting to more conveniently control the next version. (See Convenient versioning)
• #48 Show the appropriate version pattern in the version format error message.