Announce: sbt 1.3.2

I’m happy to announce sbt 1.3.2 patch release is available. Full release note is here - https://github.com/sbt/sbt/releases/tag/v1.3.2

How to upgrade

Normally changing the project/build.properties to

sbt.version=1.3.2

would be ok. However, given that this release contains fixes to sbt bash script and also because your initial resolution would be faster with *.(zip|tgz|msi) that contains all the JAR files, we recommend you use the installer distribution. They are available from Homebrew, SDKMAN, scoop, etc.

Fixes with compatibility implication

  • sbt launcher script drops -XX:+UseParallelGC for JDK 9 and up since it could cause severe GC pauses given a large heap sbt/sbt-launcher-package#282 / #5045 by @eed3si9n
  • Updates to lm-coursier-shaded 2.0.0-RC3-4, which fixes the handling of Basic auth.

Highlights

  • Updates to Scala 2.12.10
  • Fixes NoClassDefFoundError at the end of run when thread keeps running after the task. Use allowZombieClassLoaders := true to opt into using classes after the task. #5081 / #5083 by @eatkins
  • Adds a new setting called includePluginResolvers (default false ).
    When set to true , the project will include resolvers from the metabuild. #5094 by @eed3si9n

See https://github.com/sbt/sbt/releases/tag/v1.3.2 for the full details.

What happened to 1.3.1?

We realized there was a bug in sbt launcher script after we released 1.3.1, so we’re skipping it. The main artifacts are identical between the 1.3.1 and 1.3.2.

Participation

sbt 1.3.2 was brought to you by 7 contributors. Ethan Atkins, Eugene Yokota (eed3si9n), Anil Kumar Myla, Dmitrii Naumenko, Kenji Yoshida (xuwei-k), Yusuke Yamada, and Tuomas Lappeteläinen. Thank you!

Thanks to everyone who’s helped improve sbt and Zinc 1 by using them, reporting bugs, improving our documentation, porting builds, porting plugins, and submitting and reviewing pull requests.

For anyone interested in helping sbt, there are many avenues for you to help, depending on your interest. If you’re interested, Contributing, “help wanted”, “good first issue” are good starting points. If you have ideas, come talk to us on sbt-contrib or on Lightbend Discuss

1 Like