Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): Update dependency sbt/sbt to v1.10.11 #1725

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 8, 2024

This PR contains the following updates:

Package Update Change
sbt/sbt patch 1.10.0 -> 1.10.11

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

sbt/sbt (sbt/sbt)

v1.10.11: 1.10.11

Compare Source

updates
🐛 bug fixes

Full Changelog: sbt/sbt@v1.10.10...v1.10.11

v1.10.10: 1.10.10

Compare Source

🐛 bug fixes

Full Changelog: sbt/sbt@v1.10.9...v1.10.10

v1.10.9: 1.10.9

Compare Source

🚀 features and other updates
🐛 bug fixes
🎬 behind the scene
new contributors

Full Changelog: sbt/sbt@v1.10.7...v1.10.9

v1.10.8: 1.10.8

Compare Source

sbt 1.10.8 is dead on arrival, please use 1.10.9 when it comes out.

v1.10.7: 1.10.7

Compare Source

🚀 features and other updates

Build directory detection

Starting 1.10.7, the sbt runner script enables build directory detection by default. This means that the sbt will exit with error when launched in a directory without build.sbt or project/, with exceptions of sbt new, sbt --script-version etc.

To override this behavior temporarily, you can use --allow-empty flag. To permanently opt out of the build directory detection, create $XDG_CONFIG_HOME/sbt/sbtopts with --allow-empty in it.

csrMavenDependencyOverride setting

sbt 1.10.7 updates Coursier from 2.1.19 → 2.1.22. sbt 1.10.7 also adds a new setting csrMavenDependencyOverride (default: false), which controls the resolution, which respects Maven dependency override mechanism, also known as bill-of-materials (BOM) POM. Since there is a performance regression in the new resolver, we are setting the default to false.

🐛 bug fixes

🎬 behind the scene

Full Changelog: sbt/sbt@v1.10.6...v1.10.7

v1.10.6: 1.10.6

Compare Source

change with compatibility implication
  • deps: lm-coursier 2.1.6, which updates Coursier 2.1.14 → 2.1.19 by @​eed3si9n in https://github.com/sbt/sbt/pull/7920

    This release changes the way "BOMs" or "dependency management" are handled during resolution, and allows users to add BOMs to a resolution. This changes the way versions are picked when BOMs or dependency management are involved, which has an impact on the resolution of libraries from many JVM ecosystems, such as Apache Spark, Springboot, Quarkus, etc.

bug fixes and updates
behind the scene
new contributors

Full Changelog: sbt/sbt@v1.10.5...v1.10.6

v1.10.5: 1.10.5

Compare Source

updates
behind the scene

Full Changelog: sbt/sbt@v1.10.4...v1.10.5

v1.10.4: 1.10.4

Compare Source

updates and bug fixes
behind the scene

Full Changelog: sbt/sbt@v1.10.3...v1.10.4

v1.10.3: 1.10.3

Compare Source

Protobuf with potential Denial of Service (CVE-2024-7254)

sbt 1.10.3 updates protobuf-java library to 3.25.5 to address CVE-2024-7254 / GHSA-735f-pc8j-v9w8, which states that while parsing unknown fields in the Protobuf Java library, a maliciously crafted message can cause a StackOverflow error. Given the nature of how Protobuf is used in Zinc as internal serialization, we think the impact of this issue is minimum. However, security software might still flag this to be an issue while using sbt or Zinc, so upgrade is advised. This issue was originally reported by @​gabrieljones and was fixed by Jerry Tan (@​Friendseeker) in zinc#1443.

@​adpi2 at Scala Center has also configured dependency graph submission to get security alerts in zinc#1448. sbt/sbt was configured by @​Friendseeker in https://github.com/sbt/sbt/pull/7746.

Reverting the invalidation of circular-dependent sources

sbt 1.10.3 reverts the initial invalidation of circular-dependent Scala source pairs.

There had been a series of incremental compiler bugs such as "Invalid superClass" and "value b is not a member of A" that would go away after clean. The root cause of these bugs were identified by @​smarter (https://github.com/sbt/zinc/issues/598#issuecomment-449028234) and @​Friendseeker to be partial compilation of circular-dependent sources where two sources A.scala and B.scala use some constructs from each other.

sbt 1.10.0 fixed this issue via https://github.com/sbt/zinc/pull/1284 by invalidating the circular-dependent pairs together. In other words, if A.scala was changed, it would immediately invalidate B.scala. It turns out, that people have been writing circular-dependent code, and this has resulted in multiple reports of Zinc's over-compilation (zinc#1420, zinc#1461). Given that the invalidation seems to affect the users more frequently than the original bug, we're going to revert the fix for now. We might bring this back with an opt-out flag later on. The revert was contributed by by Li Haoyi (@​lihaoyi) in https://github.com/sbt/zinc/pull/1462.

Improvement: ParallelGzipOutputStream

sbt 1.10.0 via https://github.com/sbt/zinc/pull/1326 added a new consistent (repeatable) formats for Analysis storage. As a minor optimization, the pull request also included an implementation of ParallelGzipOutputStream, which would reduce the generate file size by 20%, but with little time penalty. Unfortunately, however, we have observed in CI that that the scala.concurrent.Future-based implementation gets stuck in a deadlock. @​Ichoran and @​Friendseeker have contributed an alternative implementation that uses Java threads directly, which fixes the issue in https://github.com/sbt/zinc/pull/1466.

bug fixes and updates

behind the scene

Full Changelog: sbt/sbt@v1.10.2...v1.10.3

v1.10.2: 1.10.2

Compare Source

Changes with compatibility implications

Updates and bug fixes

Behind the scenes

New contributors

Full Changelog: sbt/sbt@v1.10.0...v1.10.2

v1.10.1: 1.10.1

Compare Source

bug fixes and updates

behind the scenes

Full Changelog: sbt/sbt@v1.10.0...v1.10.1


Configuration

📅 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from j5ik2o as a code owner July 8, 2024 01:32
@renovate renovate bot enabled auto-merge (rebase) July 8, 2024 01:32
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from 94890c5 to 9e280dc Compare September 16, 2024 04:02
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.1 chore(deps): Update dependency sbt/sbt to v1.10.2 Sep 16, 2024
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from 9e280dc to 7f5c7be Compare October 20, 2024 04:32
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.2 chore(deps): Update dependency sbt/sbt to v1.10.3 Oct 20, 2024
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.3 chore(deps): Update dependency sbt/sbt to v1.10.4 Oct 28, 2024
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch 2 times, most recently from cbadcfa to 4787fe5 Compare November 4, 2024 05:03
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.4 chore(deps): Update dependency sbt/sbt to v1.10.5 Nov 4, 2024
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from 4787fe5 to 2a83724 Compare November 30, 2024 07:47
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.5 chore(deps): Update dependency sbt/sbt to v1.10.6 Nov 30, 2024
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from 2a83724 to ad3b103 Compare December 23, 2024 05:37
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.6 chore(deps): Update dependency sbt/sbt to v1.10.7 Dec 23, 2024
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from ad3b103 to 2f512ed Compare March 4, 2025 01:25
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.7 chore(deps): Update dependency sbt/sbt to v1.10.9 Mar 4, 2025
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.9 chore(deps): Update dependency sbt/sbt to v1.10.10 Mar 4, 2025
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from 2f512ed to 93cd4c6 Compare March 4, 2025 08:34
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from 93cd4c6 to 60f621f Compare March 17, 2025 09:53
@renovate renovate bot changed the title chore(deps): Update dependency sbt/sbt to v1.10.10 chore(deps): Update dependency sbt/sbt to v1.10.11 Mar 17, 2025
@renovate renovate bot force-pushed the renovate/sbt-sbt-1.x branch from 60f621f to 83749f6 Compare March 26, 2025 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants