chore(deps): update dependency sbt/sbt to v1.9.7 #52
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.2
->1.9.7
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
sbt/sbt (sbt/sbt)
v1.9.7
: 1.9.7Compare Source
Highlights
IO.unzip
. This was discovered and reported by Kenji Yoshida (@xuwei-k), and fixed by @eed3si9n in io#360.Zip Slip (arbitrary file write) vulnerability
See GHSA-h9mw-grgx-2fhf for the most up to date information. This affects all sbt versions prior to 1.9.7.
Path traversal vulnerabilty was discovered in
IO.unzip
code. This is a very common vulnerability known as Zip Slip, and was found and fixed in plexus-archiver, Ant, etc.Given a specially crafted zip or JAR file,
IO.unzip
allows writing of arbitrary file. The follow is an example of a malicious entry:When executed on some path with six levels,
IO.unzip
could then overwrite a file under/root/
. sbt main usesIO.unzip
only inpullRemoteCache
andResolvers.remote
, however, many projects useIO.unzip(...)
directly to implement custom tasks and tests.Non-determinism from AutoPlugins loading
We've known that occasionally some builds non-deterministically flip-flops its behavior when a task or a setting is set by two independent AutoPlugins, i.e. two plugins that neither depends on the other.
sbt 1.9.7 attempts to fix non-determinism of plugin loading order.
This was contributed by @eed3si9n in #7404.
Other updates and fixes
.sbtopts
support forsbt
runner script on Windows by @ptrdom in #7393scriptedSbt
key by @mdedetrich in #7383dependencyBrowseTree
log by @mkurz in #7396v1.9.6
: 1.9.6Compare Source
bug fix
Full Changelog: sbt/sbt@v1.9.5...v1.9.6
v1.9.5
: 1.9.5Compare Source
Update:⚠️ sbt 1.9.5 is broken, because it causes Scala compiler to generate wrong class names for anonymous class on lambda. While we investigate please refrain from publishing libraries with it.
https://github.com/scala/bug/issues/12868#issuecomment-1720848704
highlights
-X
is passed toscalacOptions
zinc#1246 by @unkarjedyother updates
NumberFormatException
inCrossVersionUtil.binaryScalaVersion
lm#426 by @HelloKunalscripted
client/server instability on Windows #7087 by @mdedetrichsbt
launcher script bug on Windows #7365 by @JD557help
command on oldshell #7358 by @azdrojowa123allModuleReports
toUpdateReport
lm#428 by @mdedetrichnew contributors
Full Changelog: sbt/sbt@v1.9.4...v1.9.5
v1.9.4
: 1.9.4Compare Source
CVE-2022-46751
CVE-2022-46751 is a security vulnerability discovered in Apache Ivy, but found also in Coursier.
With coordination with Apache Foundation, Adrien Piquerez (@adpi2) from Scala Center backported the fix to both our Ivy 2.3 fork and Coursier. sbt 1.9.4 updates them to the fixed versions.
Other updates
sbt_script
lookup by replacing all spaces with%20
(not only the first one) in the path. by @arturaz in https://github.com/sbt/sbt/pull/7349conscriptConfigs
task, not used and needed(?) anymore by @mkurz in https://github.com/sbt/sbt/pull/7353sbt new
menu by @SethTisue in https://github.com/sbt/sbt/pull/7354new contributors
Full Changelog: sbt/sbt@v1.9.3...v1.9.4
v1.9.3
: 1.9.3Compare Source
Actionable diagnostics (aka quickfix)
Actionable diagnostics, or quickfix, is an area in Scala tooling that's been getting attention since Chris Kipp presented it in the March 2023 Tooling Summit. Chris has written the roadmap and sent sbt/sbt#7242 that kickstarted the effort, but now there's been steady progress in Build Server Protocol, Dotty, Scala 2.13, IntelliJ, Zinc, etc. Metals 1.0.0, for example, is now capable of surfacing code actions as a quickfix.
sbt 1.9.3 adds a new interface called
AnalysisCallback2
to relay code actions from the compiler(s) to Zinc's Analysis file. Future version of Scala 2.13.x (and hopefully Scala 3) will release with proper code actions, but as a demo I've implemented a code action for procedure syntax usages even on current Scala 2.13.11 with-deprecation
flag.This was contributed by Eugene Yokota (@eed3si9n) in zinc#1226. Special thanks to @lrytz for identifying this issue in zinc#1214.
other updates
Full Changelog: sbt/sbt@v1.9.2...v1.9.3
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.