Update sbt to 1.12.14#6474
Open
mrdziuban wants to merge 1 commit into
Open
Conversation
Prior to v1.11.1, sbt had a memory leak (sbt/sbt#8142) in its `update` task that caused memory usage to grow linearly with the number of `update`s performed. This affects regular development as `update` is called as part of the `compile` task dependency graph. After upgrading to a version that includes the fix (coursier/sbt-coursier#563, coursier/sbt-coursier#564), I've found development with sbt, especially with long-running sbt shell sessions, to be a more pleasant experience; there's less sluggishness and a lot fewer warnings that say "X seconds of the last 10 seconds were spent in garbage collection." Signed-off-by: Matt Dziuban <mrdziuban@gmail.com>
mrdziuban
commented
Jul 20, 2026
| scalacOptions ++= Seq("-Wconf:src=src_managed/.*:silent"), | ||
| // Needed to be able to resolve scalafmt snapshot versions | ||
| resolvers ++= Resolver.sonatypeOssRepos("snapshots"), | ||
| resolvers += Resolver.sonatypeCentralSnapshots, |
Author
There was a problem hiding this comment.
sonatypeOssRepos was deprecated in sbt 1.11.2. The build still loads but produces a new warning:
warning: method sonatypeOssRepos in class ResolverFunctions is deprecated (since 1.11.2): Sonatype OSS Repository Hosting (OSSRH) was sunset on 2025-06-30; remove this resolver. If snapshots are required, use:
resolvers += Resolver.sonatypeCentralSnapshots
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prior to v1.11.1, sbt had a memory leak (sbt/sbt#8142) in its
updatetask that caused memory usage to grow linearly with the number ofupdates performed. This affects regular development asupdateis called as part of thecompiletask dependency graph.After upgrading to a version that includes the fix (coursier/sbt-coursier#563, coursier/sbt-coursier#564), I've found development with sbt, especially with long-running sbt shell sessions, to be a more pleasant experience; there's less sluggishness and a lot fewer warnings that say "X seconds of the last 10 seconds were spent in garbage collection."
Pull Request Checklist
Cluster Testing
/cluster_teston this PR to request it, and ping someone with access to the DA-internal system to approve it./upgrade_teston this PR to request it, and ping someone with access to the DA-internal system to approve it./hdm_teston this PR to request it, and ping someone with access to the DA-internal system to approve it./lsu_teston this PR to request it, and ping someone with access to the DA-internal system to approve it.PR Guidelines
Fixes #n, and mention issues worked on using#nMerge Guidelines