Update dependency sbt/sbt to v1.10.1 #463
Merged
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.
This PR contains the following updates:
1.9.9
->1.10.1
Release Notes
sbt/sbt (sbt/sbt)
v1.10.1
: 1.10.1Compare Source
bug fixes and updates
expandMavenSettings
by @desbo in https://github.com/sbt/librarymanagement/pull/444Map
andLList
in sjson-new 0.10.1 by @steinybot + @eed3si9n in https://github.com/eed3si9n/sjson-new/pull/142forceUpdatePeriod
by @adpi2 in https://github.com/sbt/sbt/pull/7567Optional
inter-project dependencies by @adpi2 in https://github.com/sbt/sbt/pull/7568jcenter
andscala-tools-releases
entries in the~/.sbt/repositories
file by @eed3si9n in https://github.com/sbt/launcher/pull/104behind the scenes
Full Changelog: sbt/sbt@v1.10.0...v1.10.1
v1.10.0
: 1.10.0Compare Source
Changes with compatibility implications
scalaVersion
can no longer be a lower 2.13.x version number than its transitive depdencies. See below for details.SIP-51 Support for Scala 2.13 Evolution
Modern Scala 2.x has kept both forward and backward binary compatibility so a library compiled using Scala 2.13.12 can be used by an application compiled with Scala 2.13.11 etc, and vice versa. The forward compatibility restricts Scala 2.x from evolving during the patch releases, so in SIP-51 Lukas Rytz at Lightbend Scala Team proposed:
Lukas has also contributed changes to sbt 1.10.0 to enforce stricter
scalaVersion
. Starting sbt 1.10.0, when a Scala 2.13.x patch version newer thanscalaVersion
is found, it will fail the build as follows:When you see the error message like above, you can fix this by updating the Scala version to the suggested version (e.g. 2.13.10):
Side note: Old timers might know that sbt 0.13.0 also introduced the idea of scala-library as a normal dependency. This created various confusions as developers expected
scalaVersion
, compiler version, and scala-library version as expected to align. With the hindsight, sbt 1.10.0 will continue to respectscalaVersion
to be the source-of-truth, but will reject bad ones at build time.This was contributed by Lukas Rytz in #7480.
Zinc fixes
IncOptions.useOptimizedSealed
not working for Scala 2.13 by @Friendseeker in zinc#1278ClassTag
instead ofManifest
by @xuwei-k in zinc#1265extraHash
to propagateTraitPrivateMembersModified
across external dependency by @Friendseeker in zinc#1289extraHash
computation by @Friendseeker in zinc#1290@inline
methods in Scala 2.x by @Friendseeker in zinc#1310-Xshow-phases
handling by @Friendseeker in zinc#1314ConsistentAnalysisFormat: new Zinc Analysis serialization
sbt 1.10.0 adds a new Zinc serialization format that is faster and repeatable, unlike the current Protobuf-based serialization. Benchmark data based on scala-library + reflect + compiler:
Since Zinc Analysis is internal to sbt, sbt 1.10.0 will enable this format by default. The following setting can be used to opt-out:
This was contributed by Stefan Zeiger at Databricks in zinc#1326.
New CommandProgress API
sbt 1.10.0 adds a new CommandProgress API.
This was contributed by Iulian Dragos at Gradle Inc in #7350.
Other updates
java.net.URL
constructor by @xuwei-k in #7398updateSbtClassifiers
task by @azdrojowa123 in #7437packageSrc
to includemanagedSources
by @Friendseeker in #7470publisher
setting by @Tammo0987 in #7475buildTarget/javacOptions
by @adpi2 in #7352noOp
field in the compile report by @adpi2 in #7496Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.