This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Update dependency io.gitlab.arturbosch.detekt:detekt-formatting to v1.18.1 (minimal) #34
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:
1.17.0
->1.18.1
Release Notes
detekt/detekt
v1.18.1
This is a point release for Detekt
1.18.0
containing bugfixes for problems that got discovered just after the release.Notable Changes
See all issues at: 1.18.1
v1.18.0
1.18.0 - 2021-08-12
We're more than excited to introduce you a next stable release of Detekt:
1.18.0
🎉This release is coming with a lot of changes, new rules, evolution in the API and stability improvements.
We want to take the opportunity to thank our contributors for testing, bug reporting and helping
us release this new version of Detekt.
Notable Changes
AvoidReferentialEquality
andBooleanPropertyNaming
(see #3924 and #3795)1.5.21
, and we're compiling withapiVersion
set to1.4
- #3956 and #38526.1
- #3830VarCouldBeVal
has been updated and now works only with type resolution to provide more precise findings - #3880Extensions.getRootArea
that is now deprecated from our codebase. This was affecting users with sporadic crashes. - #3848@Configuration
while auto-correction capability should be specified with the@AutoCorrectable
annotation #3820.Migration
input
property inside thedetekt{}
extension of the Gradle plugin tosource
. Theinput
property has been deprecated, and we invite you to migrate to the new property (see #3951)valueOrDefault
andvalueOrDefaultCommaSeparated
is no longer recommended. While both will remain part of the public api, they should be replaced by one of the config delegates (see #3891). The key that is used to lookup the configured value is derived from the property name.ThresholdRule
andLazyRegex
have been marked as deprecated and will be removed in a future release. Please migrate to config delegates.detekt-bom
artifact. This change should not affect anyone. If it affects you, please let us know.Changelog
Dependency Updates
Housekeeping & Refactorings
See all issues at: 1.18.0
v1.17.1
Notable Changes
This is a patch release for Detekt
1.17.0
including fixes that we considered worth a point release.Specifically, we're reverting a change on our Gradle Plugin. The original change #3655 resulted in several false positives when using rules with Type Resolution on Java/Kotlin mixed codebases.
Moreover we included a couple of false positive fixes for
NoNameShadowing
andUnnecessaryLet
Changelog
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.