5.0.1

What's Changed

• Fixes dynverAssertTagVersion by @eed3si9n in #255
• Update sbt-mima-plugin to 1.1.2 by @scala-steward in #240
• Update scalacheck to 1.17.0 by @scala-steward in #237
• Update sbt-ci-release to 1.5.11 by @scala-steward in #250
• Update org.eclipse.jgit to 5.13.1.202206130422-r by @scala-steward in #232
• Update sbt to 1.9.0-RC1 by @scala-steward in #256
• docs: small updates to the README and mention of the standalone library by @ckipp01 in #251

Full Changelog: v5.0.0...v5.0.1

5.0.0

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

• sbt-dynver is published under com.github.sbt organization by @mkurz in #242 and @ckipp01 in #244

Fixes

• Uses moduleName rather than name in mimaPreviousArtifacts by @sideeffffect in #174

Behind the scene

• Uses sbt-ci-release to publish to Maven Central by @mkurz in #242 and @ckipp01 in #244
• Drop sbt 0.13 (and thus Scala 2.10) by @dwijnand in #176
• Encodes sbt cross building in terms of Scala cross by @eed3si9n in #247
• Starts cross publishing the dynver package by @ckipp01 in #245
• Updates references of master to main by @ckipp01 in #246
• Prep for CLI introduction by @dwijnand in #195
• Split into library and sbt plugin by @dwijnand in #193
• Switches to GitHub Actions & drops Mergify too by @dwijnand in #220
• Tweaks publishing from plugin/lib splitting by @dwijnand in #196
• Updates GitHub repo url by @xuwei-k in #243
• Updates mimaPreviousVersion to 5.0.0-M3 by @dwijnand in #198
• Updates org.eclipse.jgit to 5.12.0.202106070339-r by @scala-steward in #216
• Uses sbt 1.9.0-M1 for POM consistency by @eed3si9n in #248
• Uses slash syntax everywhere by @SethTisue in #201

New Contributors

• @SethTisue made their first contribution in #201
• @xuwei-k made their first contribution in #243
• @ckipp01 made their first contribution in #244
• @mkurz made their first contribution in #242
• @eed3si9n made their first contribution in #247

Full Changelog: v4.1.1...v5.0.0

5.0.0-M3

Changes

• Tweak publishing from plugin/lib splitting. #196 by @dwijnand
• Prep for CLI introduction. #195 by @dwijnand

v5.0.0-M2...v5.0.0-M3

5.0.0-M2

Changes

• Fix the bintray settings. #194 by @dwijnand

v5.0.0-M1...v5.0.0-M2

5.0.0-M1

Changes

• Split into library and sbt plugin. #193 by @dwijnand
• Drop sbt 0.13 (and thus Scala 2.10). #176 by @dwijnand
• Use moduleName rather than name in mimaPreviousArtifacts. #174 by @sideeffffect

v4.1.1...v5.0.0-M1

4.1.1

Changes

• Fix tagPrefix/vTagPrefix coherence. #170 by @dwijnand

v4.1.0...4.1.1

4.1.0

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

v4.0.0...4.1.0

4.0.0

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

v3.3.0...v3.4.0

3.3.0

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

v3.2.0...v3.3.0

3.2.0

• 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

v3.1.0...v3.2.0