-
Notifications
You must be signed in to change notification settings - Fork 185
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 metaconfig-typesafe-config to 0.9.16 #1522
Update metaconfig-typesafe-config to 0.9.16 #1522
Conversation
5ce2119
to
364db76
Compare
It looks like c66f24d has no effect since https://github.com/scalacenter/scalafix/pull/907/files#diff-fa445c2f97a1bfb229caa4cd2fdc97cb9c243ddac155698a132bcbdb22970910R91 |
364db76
to
f303fe7
Compare
|
@bjaglin it should be possible to work around it similar to how I did it in mdoc: https://github.com/scalameta/mdoc/pull/603/files#diff-a8b31f6574d70bc4d9f927ba67d848b1161bceb085b9248a50f50338c70bfac7R304 |
This reverts commit c66f24d, which was no longer used since 1547da5, and no longer compiles with the metaconfig bump bringing com-lihaoyi/PPrint#72 .
f303fe7
to
eb894c4
Compare
pprint.TPrint (brough by metaconfig) has now 2 different signatures because metaconfig is pinned for 2.11. // scala 2.11 trait TPrint[T] { def render(implicit tpc: TPrintColors): String } // scala 2.12+ trait TPrint[T] { def render(implicit tpc: TPrintColors): fansi.Str }
eb894c4
to
de374ad
Compare
@tgodzik thanks for the pointer! It turned out to be a bit more convoluted because of scalafix/project/Dependencies.scala Line 26 in de374ad
scala-2.11 source files to compile.
However, there seems to be a bigger problem: the breaking changes in
I'll follow-up in scalameta/metaconfig#151 |
@@ -24,7 +24,7 @@ object Dependencies { | |||
val java8CompatV = "0.9.0" | |||
val jgitV = "5.13.0.202109080827-r" | |||
val metaconfigFor211V = "0.9.10" // metaconfig stops publishing for scala 2.11 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to publish scalafix for 2.11
though? Isn't metaconfig only needed for CLI/sbt ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Scalafix must be published in 2.11 for ExplicitResultTypes
to work against 2.11 sources. This is something we can challenge though.
metaconfig is included in community rules projects via scalafix-core
and is documented
$ cs resolve -t com.github.liancheng::organize-imports:0.6.0
└─ com.github.liancheng:organize-imports_2.13:0.6.0
├─ ch.epfl.scala:scalafix-core_2.13:0.9.31
│ ├─ com.geirsson:metaconfig-typesafe-config_2.13:0.9.14
│ │ ├─ com.geirsson:metaconfig-core_2.13:0.9.14
Following up in #1530 seems that steward gets confused on which artifacts gets bumped) which should unblock the situation as discussed in scalameta/metaconfig#154 (comment). |
Updates com.geirsson:metaconfig-typesafe-config from 0.9.15 to 0.9.16.
GitHub Release Notes - Version Diff
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!
Files still referring to the old version number
The following files still refer to the old version number (0.9.15).
You might want to review and update them manually.
Ignore future updates
Add this to your
.scala-steward.conf
file to ignore future updates of this dependency:labels: library-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1