Update scalafix.version to v0.10.1 - autoclosed #214
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.9.31
->0.10.1
0.9.31
->0.10.1
Release Notes
scalacenter/scalafix
v0.10.1
Compare Source
Pull Requests
v0.10.0
Compare Source
Significant changes since v0.9.34
For users
Scalafix will now issue a warning when loading external rules built with a potentially non-compatible version of Scalafix. Until new versions of these external rules are published, it istherefore expected that you get that warning, for example with
OrganizeImports
v0.6.0:Note that most community rules (including
OrganizeImports
) will work just fine despite this warning as the breaking changes in 0.10.x are very limited.For rule authors
metaconfig-pprint
to limit the impact of a breaking change incom.lihaoyi::pprint:0.7.0
(see https://github.com/com-lihaoyi/PPrint/pull/72 & https://github.com/scalameta/metaconfig/pull/154). External rules had no reason to directly use the PPrint classes, but ithe nternal usage of PPrint in metaconfig'sderive*
macros (used for the configuration case classes) means that a recompilation is needed.scalafix-cli:0.10.x
bringscom.lihaoyi::pprint:0.6.6
so that configurable rules compiled againstscalafix-core:0.9.x
can runscalafix-core:0.10.x
will cause cryptic runtime failures withscalafix-cli:0.9.x
, so you should reflect that by releasing your rule built againstscalafix-core:0.10.x
with a major bump, and ideally by adding documentation describing your compatibility matrix.Pull Requests
Rules
ExplicitResultTypes
: backquote types when needed (#1578) @danichegFramework
Docs
CONTRIBUTING.md
(#1584) @danichegUpdates
v0.9.34
Compare Source
Pull Requests
v0.9.33
Compare Source
Pull Requests
v0.9.32
Compare Source
Pull Requests
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.