Sbt Dynver Versions Save

An sbt plugin to dynamically set your version from git

v5.0.1

1 year ago

What's Changed

Full Changelog: https://github.com/sbt/sbt-dynver/compare/v5.0.0...v5.0.1

v5.0.0

1 year ago

About sbt-dynver

sbt-dynver is an sbt plugin, originally developed by Dale Wijnand (@dwijnand) in 2016, to dynamically set the version of an sbt build based on git.

sbt-dynver is published to Maven Central for sbt 1.x for both the traditional POM-inconsistent style (sbt-dynver-5.0.0.pom) and POM-consistent style (sbt-dynver_2.12_1.0-5.0.0.pom).

Change with compatibility implications

Fixes

Behind the scene

New Contributors

Full Changelog: https://github.com/sbt/sbt-dynver/compare/v4.1.1...v5.0.0

v5.0.0-M3

3 years ago

Changes

https://github.com/dwijnand/sbt-dynver/compare/v5.0.0-M2...v5.0.0-M3

v5.0.0-M2

3 years ago

v5.0.0-M1

3 years ago

Changes

https://github.com/dwijnand/sbt-dynver/compare/v4.1.1...v5.0.0-M1

v4.1.1

3 years ago

Changes

https://github.com/dwijnand/sbt-dynver/compare/v4.1.0...4.1.1

v4.1.0

3 years ago

Enhancements

Allow arbitrary tag prefixes

Originally the detection of version tags in sbt-dynver simply used the practice of adding a "v" prefix in tag, such as "v1.2.3". Later, in 4.0.0, support was added to opt-out of the "v" with dynverVTagPrefix, allowing projects that never followed this practice to adopt sbt-dynver.

With the release of sbt-dynver 4.1.0, dynverVTagPrefix has been generalised with dynverTagPrefix.

You can continue to use dynverVTagPrefix for the simple opt-out use case:

dynverVTagPrefix in ThisBuild := false

but if your project uses another prefix it now maybe possible for you to use sbt-dynver by setting the new key:

dynverTagPrefix in ThisBuild := "foo-" // our tags have the format foo-<version>, e.g. foo-1.2.3

Setting both to incoherent values will throw an exception at build loading time.

#158 by @eliaslevy/@sideeffffect/@dwijnand

Other changes

Fix dynverAssertTagVersion

Previously when used in onGlobal it errored with "A setting cannot depend on a task".

#132/#137 by @steinybot/@dwijnand

Changelog

https://github.com/dwijnand/sbt-dynver/compare/v4.0.0...4.1.0

v4.0.0

4 years ago

Breaking changes

  • Change the version scheme of untagged versions so they are never considered newer than tagged versions. For instance, previously the 3rd commit in a repo would generate a version like 3-1234abcd; that is now 0.0.0+3-1234abcd. #99/#100 by @Atry!

Other changes

  • Introduces dynverSeparator to change the separator string between a version, its HEAD commit distance & SHA, and the timestamp. For instance, for Docker-compatible version strings set dynverSeparator in ThisBuild := "-". #5/#91 by @jroper!
  • Fix dynverGitPreviousStableVersion to use the same tag matching semantics the rest of sbt-dynver uses. #104 by @2m!
  • Introduces dynverVTagPrefix to (finally?) allow tags to not be 'v'-prefixed. Set dynverVTagPrefix in ThisBuild := false to make this change. #108/#110 by @dwijnand

https://github.com/dwijnand/sbt-dynver/compare/v3.3.0...v3.4.0

v3.3.0

5 years ago
  • Support dynverSonatypeSnapshots in dynver, dynverAssertVersion, and dynverCheckVersion. #89/#90

https://github.com/dwijnand/sbt-dynver/compare/v3.2.0...v3.3.0

v3.2.0

5 years ago
  • Document dynverSonatypeSnapshots setting. #82 by @qingwei91
  • Make isVersionStable a SettingKey. #83
  • Document how to sanity check versions are derived from a tag. #86
  • Introduce dynverAssertTagVersion. #87
  • Add FAQ for skipping binary compatibility check for major version branches. #88 by @jatcwang

https://github.com/dwijnand/sbt-dynver/compare/v3.1.0...v3.2.0