syedmurtaza108 / chucker-flutter

An HTTP requests inspector inspired by Chucker Android
https://pub.dev/packages/chucker_flutter
MIT License
54 stars 32 forks source link

chore(deps): update dependency gradle to v6.9.4 #33

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Update Change
gradle (source) minor 6.7 -> 6.9.4

Release Notes

gradle/gradle ### [`v6.9.4`](https://togithub.com/gradle/gradle/releases/tag/v6.9.4): 6.9.4 This is a patch release for 6.9. We recommend using 6.9.4 instead of 6.9. It fixes the following issues: - [#​23680](https://togithub.com/gradle/gradle/issues/23680) Dependency graph resolution: Equivalent excludes can cause un-necessary graph mutations \[backport 6.x] - [#​23945](https://togithub.com/gradle/gradle/issues/23945) Backport trusting only full GPG keys in dependency verification \[Backport 6.9.4] - [#​23950](https://togithub.com/gradle/gradle/issues/23950) Exclude rule merging: missing optimization \[backport 6.x] [Read the Release Notes](https://docs.gradle.org/6.9.4/release-notes.html) #### Upgrade Instructions Switch your build to use Gradle 6.9.4 by updating your wrapper: ./gradlew wrapper --gradle-version=6.9.4 See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.9.4/userguide/upgrading_version\_6.html#changes\_6.9) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.9.4. #### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v6.9.3`](https://togithub.com/gradle/gradle/releases/tag/v6.9.3): 6.9.3 This is a patch release for Gradle 6.9, containing backported bugfixes in Gradle 7.x to Gradle 6.x. It fixes the following issues: - [#​19523](https://togithub.com/gradle/gradle/issues/19523) Fix buffer overflow error in KryoBackedDecoder \[Backport 6.x] - [#​20189](https://togithub.com/gradle/gradle/issues/20189) Support constraints without version in GMM \[Backport 6.9.x] - [#​22358](https://togithub.com/gradle/gradle/issues/22358) Missing exclude rule merging optimizations We recommend users upgrade to 6.9.3 instead of 6.9. #### Upgrade Instructions Switch your build to use Gradle 6.9.3 by updating your wrapper: ./gradlew wrapper --gradle-version=6.9.3 See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.9.3/userguide/upgrading_version\_6.html#changes\_6.9) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.9.3. #### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v6.9.2`](https://togithub.com/gradle/gradle/releases/tag/v6.9.2): 6.9.2 This is a patch release for Gradle 6.9, containing backported bugfixes in Gradle 7.2 to Gradle 6.x. It fixes the following issues: - [#​18163](https://togithub.com/gradle/gradle/issues/18163) Fix excludes for substituted dependencies - [#​18164](https://togithub.com/gradle/gradle/issues/18164) POSIX shell scripts improvements - [#​18697](https://togithub.com/gradle/gradle/issues/18697) Fix corrupted resolution result from replacement / capability conflict - [#​19328](https://togithub.com/gradle/gradle/issues/19328) Mitigations for log4j vulnerability in Gradle builds - [#​19372](https://togithub.com/gradle/gradle/issues/19372) Multiple transformed artifacts selected We recommend users upgrade to 6.9.2 instead of 6.9. Given the context of the Log4Shell vulnerability, make sure you take a look at [our blog post](https://blog.gradle.org/log4j-vulnerability) on this topic. #### Upgrade Instructions Switch your build to use Gradle 6.9.2 by updating your wrapper: ./gradlew wrapper --gradle-version=6.9.2 See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.9.2/userguide/upgrading_version\_6.html#changes\_6.9) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.9.2. #### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v6.9.1`](https://togithub.com/gradle/gradle/releases/tag/v6.9.1): 6.9.1 This is a patch release for Gradle 6.9, containing backported bugfixes in Gradle 7.2 to Gradle 6.x. It fixes the following issues: - [#​18089](https://togithub.com/gradle/gradle/issues/18089) Deprecate jcenter() repository - [#​17950](https://togithub.com/gradle/gradle/issues/17950) Renaming and recreating the project directory causes Gradle to lose track of changes on Windows - [#​17949](https://togithub.com/gradle/gradle/issues/17949) Gradle's up-to-date checks do not work on Windows FAT drives We recommend users upgrade to 6.9.1 instead of 6.9. #### Upgrade Instructions Switch your build to use Gradle 6.9.1 by updating your wrapper: ./gradlew wrapper --gradle-version=6.9.1 See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.9.1/userguide/upgrading_version\_6.html#changes\_6.9) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.9.1. #### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v6.8.3`](https://togithub.com/gradle/gradle/releases/tag/v6.8.3): 6.8.3 This is a patch release for Gradle 6.8. This fixes [a critical bug](https://togithub.com/gradle/gradle/issues/16144) present in Gradle 6.8, 6.8.1 and 6.8.2. [All issues fixed in this patch release](https://togithub.com/gradle/gradle/milestone/171?closed=1) Please don’t use the original 6.8 release or previous patch releases, and instead upgrade to 6.8.3. #### Upgrade Instructions Switch your build to use Gradle 6.8.3 by updating your wrapper: ./gradlew wrapper --gradle-version=6.8.3 --gradle-distribution-sha256-sum 7faa7198769f872826c8ef4f1450f839ec27f0b4d5d1e51bade63667cbccd205 See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.8.3/userguide/upgrading_version\_6.html#changes\_6.8) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.8.3. #### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v6.8.2`](https://togithub.com/gradle/gradle/releases/tag/v6.8.2): 6.8.2 This is a patch release for Gradle 6.8. This fixes several bugs in Gradle 6.8.1. [All issues fixed in this patch release](https://togithub.com/gradle/gradle/milestone/170?closed=1) Please don’t use the original 6.8 release or the 6.8.1, and instead upgrade to 6.8.2. ##### Upgrade Instructions Switch your build to use Gradle 6.8.2 by updating your wrapper: `./gradlew wrapper --gradle-version=6.8.2` See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.8.2/userguide/upgrading_version\_6.html#changes\_6.8) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.8.2. ##### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v6.8.1`](https://togithub.com/gradle/gradle/releases/tag/v6.8.1): 6.8.1 This is a patch release for Gradle 6.8. This fixes several critical bugs in Gradle 6.8. [All issues fixed in this patch release](https://togithub.com/gradle/gradle/milestone/168?closed=1) We recommend that you use Gradle 6.8.1 over the initial release of Gradle 6.8. ##### Upgrade Instructions Switch your build to use Gradle 6.8.1 by updating your wrapper: `./gradlew wrapper --gradle-version=6.8.1` See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.8.1/userguide/upgrading_version\_6.html#changes\_6.8) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.8.1. ##### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v6.7.1`](https://togithub.com/gradle/gradle/releases/tag/v6.7.1): 6.7.1 This is a patch release for Gradle 6.7. This fixes several critical bugs in Gradle 6.7. [All issues fixed in this patch release](https://togithub.com/gradle/gradle/milestone/160?closed=1) We recommend that you use Gradle 6.7.1 over the initial release of Gradle 6.7. ##### Upgrade Instructions Switch your build to use Gradle 6.7.1 by updating your wrapper: `./gradlew wrapper --gradle-version=6.7.1` See the [Gradle 6.x upgrade guide](https://docs.gradle.org/6.7.1/userguide/upgrading_version\_6.html#changes\_6.7) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.7.1. ##### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss).

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 this update again.



This PR has been generated by Mend Renovate. View repository job log here.

codecov-commenter commented 1 year ago

Codecov Report

Patch and project coverage have no change.

Comparison is base (f9b823e) 92.24% compared to head (7c18093) 92.24%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #33 +/- ## ======================================= Coverage 92.24% 92.24% ======================================= Files 37 37 Lines 1521 1521 ======================================= Hits 1403 1403 Misses 118 118 ``` Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Syed+Murtaza). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Syed+Murtaza)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

renovate[bot] commented 1 year ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (6.9.4). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.