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

Update sbt to 1.10.0 #4023

Closed
wants to merge 1 commit into from
Closed

Update sbt to 1.10.0 #4023

wants to merge 1 commit into from

Conversation

scalameta-bot
Copy link
Contributor

About this PR

πŸ“¦ Updates org.scala-sbt:sbt from 1.9.9 to 1.10.0

πŸ“œ 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", artifactId = "sbt" } ]

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

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

@kitbellew
Copy link
Collaborator

@tgodzik what was the magic you did with scalameta, to make this work? :)

@tgodzik
Copy link
Contributor

tgodzik commented Jun 24, 2024

@tgodzik what was the magic you did with scalameta, to make this work? :)

I had to make sure that all the libraries use the same or older Scala version as the current one. I can take a look here and fix it for you, should be quick

@tgodzik
Copy link
Contributor

tgodzik commented Jun 25, 2024

Wait, don't we just have to update scalaVersion to 2.13.14 ? It seems some artifacts such as scalameta use that and we should always use the latest.

@tgodzik
Copy link
Contributor

tgodzik commented Jun 25, 2024

The only option to update sbt is to change the artifacts to ones using Scala 2.13.13, or wait until the jline is updated for Scala 2.13.15

@scalameta-bot
Copy link
Contributor Author

Superseded by #4109.

@scalameta-bot scalameta-bot deleted the update/sbt-1.10.0 branch July 22, 2024 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants