Skip to content

Conversation

@scala-steward
Copy link
Contributor

About this PR

📦 Updates com.github.sbt:sbt-ci-release from 1.5.10 to 1.5.12

📜 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 = "com.github.sbt", artifactId = "sbt-ci-release" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.sbt", artifactId = "sbt-ci-release" }
}]
labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

@scala-steward scala-steward force-pushed the update/sbt-ci-release-1.5.12 branch from f56a107 to 78889bd Compare May 5, 2023 19:18
@SethTisue
Copy link
Collaborator

java.lang.RuntimeException: Some keys were defined with the same name but different types: 'gitReader' (com.github.sbt.git.ReadableGit, com.typesafe.sbt.git.ReadableGit), 'gitRunner' (sbt.Task[com.github.sbt.git.GitRunner], sbt.Task[com.typesafe.sbt.git.GitRunner])

I think what's going on here is that https://github.com/sbt/sbt-git changed packages, and sbt-ci-release is pulling in the new one but sbt-prompt is pulling in the old one

@SethTisue
Copy link
Collaborator

sbt-prompt is unmaintained (last commit 5 years ago) and inessential, so I'll add a commit that removes it

it was causing a dependency conflict (over sbt-git version) with
the latest sbt-ci-release. but anyway, the plugin is unmaintained
(no commits in 5 years) and is just a nicety anyway
@SethTisue SethTisue merged commit 99f60c7 into lightbend-labs:main May 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants