I'm happy to announce sbt 1.5.4 patch release is available. Full release note is here - https://github.com/sbt/sbt/releases/tag/v1.5.4

• Fixes compiler ClassLoader list to use compilerJars.toList (For Scala 3, this drops support for 3.0.0-M2) #6538 by @adpi2
• Fixes undercompilation of package object causing "Symbol 'type X' is missing from the classpath" zinc#983 by @retronym
• Fixes overcompilation with scalac -release flag zinc#982 by @retronym
• Fixes BSP on ARM Macs by keeping JNI server socket to keep using JNI ipcsocket#14 by @quelgar

In June of 2011, I started working on sbt-assembly for sbt 0.10, based on Coda Hale's assembly-sbt from sbt 0.7, which in turn was probably inspired by maven-assembly-plugin. After ten years, I'm going to call this one 1.0.0. sbt-assembly 1.0.0 is published to Maven Central.

• Fixes scalacOptions not getting forwarded to ScalaDoc in Scala 3 #6499 by @pikinier20
• Fixes undercompilation of sealed traits that extends other seal traits zinc#979 by @dwijnand
• Fixes version parsing not recognizing dots in a prerelease tag lm#377 by @Nirvikalpa108
• Fixes inputFile resolving to incorrect files when file specific globs are used io#319 by @eatkins
• Updates to Scala 2.12.14 #6522 by @mkurz

For more details please see https://github.com/sbt/sbt/releases/tag/v1.5.3

Spotify: https://open.spotify.com/playlist/5Q7NulW7CU4HnNyyQpdR6Z?si=3ea3c66015e5...
YouTube: https://www.youtube.com/playlist?list=PLSUh6oJ5ZotUNhE96_iH0Z6d_1uY8wk4T

There's a long-standing bug that sbt maintainers have known for a while, which is that when sbt plugin is published to a Maven repository, the POM file sbt generates is not valid.

Here's an example. sbt-pgp 2.1.2 is published to https://repo1.maven.org/maven2/com/github/sbt/sbt-pgp_2.12_1.0/2.1.2/sbt-pgp-2.1.2.pom, but if you look at the POM file name it's sbt-pgp-2.1.2.pom, not matching the URL structure sbt-pgp_2.12_1.0. Since most plugins were published to Bintray until recently, and because only a few plugins were published to Sonatype OSSRH, which seems to be okay with this, this issue has not gotten too much attention.

Fast forward 2021, Bintray was discontinued, and now that more plugins are published to Sonatype OSSRH, companies that use Artifactory to front Maven Central are running into this. Active GitHub issue is sbt/sbt#3410. I will discuss an experimental workaround for this.

I'm happy to announce sbt 1.5.2 patch release is available. Full release note is here - https://github.com/sbt/sbt/releases/tag/v1.5.2

• Fixes sbt new leaving behind target directory #6488 by @eed3si9n
• Fixes ConcurrentModificationException while compiling Scala 2.13.4 and Java sources zinc#974 by @lefou
• Improved developer guide for new contributors #6469 by @Nirvikalpa108
• Fixes -client by making it the same as --client #6500 by @Nirvikalpa108
• Uses -Duser.home instead of $HOME to download launcher JAR #6483 by @rdesgroppes

I'm happy to announce sbt 1.5.1 patch release is available. Full release note is here - https://github.com/sbt/sbt/releases/tag/v1.5.1. This post will also report the Bintray to JFrog Artifactory migration.

There's now a cloud-hosted Artifactory instance licensed to Scala Center. Let's call this "Artsy" in this post instead of the Artifactory instance. With the release of sbt 1.5.1, I think we can say that the migration is done.

Wrote herding cats: day 19 featuring FunctionK, or Rúnar's encoding of rank-2 polymorphic function, and Resource datatype, which he envisioned rank-N polymorphism would unlock back in 2010.

Hi everyone. On behalf of the sbt project, I am happy to announce sbt 1.5.0. This is the fifth feature release of sbt 1.x, a binary compatible release focusing on new features. sbt 1.x is released under Semantic Versioning, and the plugins are expected to work throughout the 1.x series.

The headline features of sbt 1.5.0 are:

• Scala 3 support
• Eviction error
• Deprecation of sbt 0.13 syntax
• Coursier-based launcher

How to upgrade