Skip to content

Update sbt, scripted-plugin to 1.12.10#753

Open
typelevel-steward[bot] wants to merge 1 commit intomainfrom
update/sbt-1.12.10
Open

Update sbt, scripted-plugin to 1.12.10#753
typelevel-steward[bot] wants to merge 1 commit intomainfrom
update/sbt-1.12.10

Conversation

@typelevel-steward
Copy link
Copy Markdown
Contributor

About this PR

📦 Updates

from 1.12.9 to 1.12.10

📜 GitHub Release Notes - Version Diff

Usage

Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scala-sbt" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt" }
}]
labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

@rossabaker
Copy link
Copy Markdown
Member

This (and a handful of others across the org) have a Scala Native mismatch in the test configuration that's now being enforced:

[error] 	* org.scala-native:test-interface_native0.5_2.12:0.5.11 (strict) is selected over 0.5.8 for test
[error] 	    +- org.typelevel:jawn-parser_native0.5_2.12:1.6.0-238-6ed94fd-SNAPSHOT (depends on 0.5.11)
[error] 	    +- org.scalacheck:scalacheck_native0.5_2.12:1.19.0    (depends on 0.5.8)

I guess it's coming from Scalacheck, but I don't know why that's incompatible.

@eed3si9n
Copy link
Copy Markdown
Collaborator

eed3si9n commented Apr 27, 2026

Recently @xuwei-k reminded me that org.scala-native:test-interface for some reasons enforces strict versionScheme

Requires exact match of version

I wonder if we can ignore it by overriding to a relaxed scheme via libraryDependencySchemes.

Looks like there's an issue for this now - scala-native/scala-native#4844

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.

2 participants