Skip to content
This repository has been archived by the owner on Jun 28, 2022. It is now read-only.

chore(deps): update dependency gradle to v7 #3354

Closed

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Apr 27, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Update Change
gradle (source) major 4.10.3 -> 7.2

Release Notes

gradle/gradle

v7.1.1

This is a patch release for Gradle 7.1.

It fixes the following issues:

  • #​17488 Many Micronaut builds failing with NPE with Gradle 7.1 & JDK 8
  • #​17548 [Configuration cache] Task not up-to-date for SantaTracker
  • #​17542 [Configuration cache] Filtered FC with mapped elements stored incorrectly

We recommend users upgrade to 7.1.1 instead of 7.1.

Upgrade Instructions

Switch your build to use Gradle 7.1.1 by updating your wrapper:

./gradlew wrapper --gradle-version=7.1.1

See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.1.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v7.0.2

This is a patch release for Gradle 7.0.

This fixes an issue with files system watching on certain Linux distributions.

We recommend users upgrade to 7.0.2 instead of 7.0.

Upgrade Instructions

Switch your build to use Gradle 7.0.2 by updating your wrapper:

./gradlew wrapper --gradle-version=7.0.2

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.0.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v7.0.1

This is a patch release for Gradle 7.0.

This fixes several issues reported against 7.0.

We recommend users upgrade to 7.0.1 instead of 7.0.

Upgrade Instructions

Switch your build to use Gradle 7.0.1 by updating your wrapper:

./gradlew wrapper --gradle-version=7.0.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.0.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.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 Deprecate jcenter() repository
  • #​17950 Renaming and recreating the project directory causes Gradle to lose track of changes on Windows
  • #​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 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 adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.9

v6.8.3

This is a patch release for Gradle 6.8.

This fixes a critical bug present in Gradle 6.8, 6.8.1 and 6.8.2.

All issues fixed in this patch release

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 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 adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.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

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 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 adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.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

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 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 adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.8

v6.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

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 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 adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.7

v6.6.1

This is a patch release for Gradle 6.6.

This fixes several critical bugs in Gradle 6.6.

All issues fixed in this patch release

We recommend that you use Gradle 6.6.1 over the initial release of Gradle 6.6.

Upgrade Instructions

Switch your build to use Gradle 6.6.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.6.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.6.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.6

v6.5.1

This is a patch release for Gradle 6.5.

This fixes several critical bugs in Gradle 6.5:

  • Regression: Gradle 6.5 cached builds cause IllegalStateException #​13367
  • Regression: Compile classpath configuration is not deterministic #​13555
  • Regression: Class cast exception when GStrings are used with System.getProperty #​13569
  • And a number of dependency graph resolution errors (#​13251, #​13316, #​13329, #​13551)

All issues fixed in this patch release

We recommend that you use Gradle 6.5.1 over the initial release of Gradle 6.5.

Upgrade Instructions

Switch your build to use Gradle 6.5.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.5.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.5.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.5

v6.4.1

This is a patch release for Gradle 6.4.

This fixes several critical bugs in Gradle 6.4:

  • Regression: Different daemons are used between IDE and CLI builds for the same project #​13069
  • Regression: Main-Class attribute always added to jar manifest when using application plugin #​13057

All issues fixed in this patch release

We recommend that you use Gradle 6.4.1 over the initial release of Gradle 6.4.

Upgrade Instructions

Switch your build to use Gradle 6.4.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.4.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.4.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.4

v6.3

v6.2.2

This is a patch release for Gradle 6.2.

This fixes a critical bug in Gradle 6.2:

  • Multi-project build use the properties of the rootProject for all included builds. #​12381

All issues fixed

We recommend that you use Gradle 6.2.2 over the initial release of Gradle 6.2.

Read the full release notes

Upgrade Instructions

Switch your build to use Gradle 6.2.2 by updating your wrapper:

./gradlew wrapper --gradle-version=6.2.2

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.2.2.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.2.1

This is a patch release for Gradle 6.2.

This fixes several critical bugs in Gradle 6.2:

  • Project name disambiguation causes project / external dependency conflicts to be missed. #​12315
  • IdeaModelBuilder does not provide groovy-all as compile dep for buildSrc #​12274
  • Gradle crashes if GRADLE_RO_DEP_CACHE is set and it cannot create modules-2 directory within it #​12293

All issues fixed

We recommend that you use Gradle 6.2.1 over the initial release of Gradle 6.2.

Read the full release notes

Upgrade Instructions

Switch your build to use Gradle 6.2.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.2.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.2.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.2

v6.1.1

This is a patch release for Gradle 6.1.

This fixes several critical bugs in Gradle 6.1:

  • Plugins using kotlin-dsl and compiled with 6.1 are incompatible with Gradle 6.0 #​11947
  • Missing fixed issues from Gradle 6.1 release notes #​11954
  • Memory regression when resolving large artifacts while computing checksums #​11966
  • Gradle 6.1 generates an empty .gradle and gradle directories on each execution in subproject directories #​11971

All issues fixed

We recommend that you use Gradle 6.1.1 over the initial release of Gradle 6.1.

Read the full release notes

Upgrade Instructions

Switch your build to use Gradle 6.1.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.1.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.1.x.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

v6.1

v6.0.1

This is a patch release for Gradle 6.0.

This fixes several critical bugs in Gradle 6.0:

  • Incremental Java compilation is broken with Android 3.5.1 and Gradle 6.0 #​11330
  • Unable to use a Provider as an artifact for the maven-publish plugin #​11054
  • Implicit capabilities not always applied/detected #​11300
  • maven-metadata.xml SHA256 and SHA512 checksums prevent publishing to Nexus #​11308
  • Unable to properly resolve dynamic dependencies from mavenLocal() repo #​11321
  • Kotlin DSL: fileTree(mapOf(...)) has unexpected behavior #​11335
  • Attribute disambiguation rule for 'org.gradle.category' can cause unexpected type exception #​11365

All issues fixed

We recommend that you use Gradle 6.0.1 over the initial release of Gradle 6.0.

Upgrade Instructions

Switch your build to use Gradle 6.0.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=6.0.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.6.4

This bug-fix release contains all changes from 5.6.1 through 5.6.3 as well as:

  • Can't configure kotlinOptions after upgrade to gradle 5.6.3 using kotlin-dsl #​11083
  • Slow localhost look-up on macOS #​11134

We recommend that you use Gradle 5.6.4 over any other 5.6.x release.

Upgrade Instructions

Switch your build to use Gradle 5.6.4 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.4

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.6.3

This bug-fix release contains all changes from 5.6.1 and 5.6.2 as well as:

  • Let Kotlin DSL gracefully handle lambdas registered as extensions (5.6.3) #​11014
  • Gradle Module Metadata compatibility for unique snapshots #​11050
  • maven-publish publishes jars with wrong extension for known jar packagings like 'ejb' in 5.6 #​10555
  • Regression in 5.5 when using dependency constraints for non-jar dependencies without a POM #​10948
  • resolution failure when dependency locks and kotlin-dsl plugin are present #​10697
  • Non-Kotlin extensions crash the build when using Kotlin DSL + Kotlin plugins #​10729
  • Sporadic build failures with build-scan due to an overlapping ID assignment https://github.com/gradle/gradle/pull/10286
  • Prevent StackOverflowException caused by excessive 'or' via PatternMatcher #​10330

We recommend that you use Gradle 5.6.3 over any other 5.6.x release.

Upgrade Instructions

Switch your build to use Gradle 5.6.3 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.3

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.6.2

This bug-fix release contains changes to Gradle 5.6.1:

  • Duplicate entry in generated .classpath file in Gradle >= 5.6 (#​10393)
  • Memory leak when using tasks that use Worker API and process isolation (#​10411)

We recommend that you use Gradle 5.6.2 over 5.6.1.

Upgrade Instructions

Switch your build to use Gradle 5.6.2 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.2

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.6.1

This bug-fix release contains changes to Gradle 5.6:

We recommend that you use Gradle 5.6.1 over 5.6.

Upgrade Instructions

Switch your build to use Gradle 5.6.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.5.1

This bug-fix release contains three changes to Gradle 5.5:

  • Combination of errorprone-gradle-plugin and options.fork = true causes Java compilation to fail in Gradle 5.5 #​9897
  • Using dependency declaration gradleKotlinDsl() fails with 5.5 #​9919
  • Chain of transitives aligned by same platform can lead to broken resolution #​9882

We recommend that you use Gradle 5.5.1 over 5.5.

Upgrade Instructions

Switch your build to use Gradle 5.5.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.5.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.4.1

This bug-fix release contains two changes to Gradle 5.4:

We recommend that you use Gradle 5.4.1 over 5.4.

Upgrade Instructions

Switch your build to use Gradle 5.4.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.4.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.3.1

This bug-fix release contains several changes to Gradle 5.3, notably:

We recommend that you use Gradle 5.3.1 over 5.3.

Upgrade Instructions

Switch your build to use Gradle 5.3.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.3.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.2.1

This bug-fix release contains several changes to Gradle 5.2, notably:

We recommend that you use Gradle 5.2.1 over 5.2.

Upgrade Instructions

Switch your build to use Gradle 5.2.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.2.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.1.1

This bug-fix release contains several changes to Gradle 5.1, notably:

We recommend that you use Gradle 5.1.1 over 5.1.

Upgrade Instructions

Switch your build to use Gradle 5.1.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.1.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.


Configuration

📅 Schedule: "after 9am and before 3pm" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box.

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

@renovate-bot renovate-bot requested a review from a team as a code owner April 27, 2021 10:18
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Apr 27, 2021
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Apr 27, 2021
@renovate-bot renovate-bot force-pushed the renovate/gradle-7.x branch 5 times, most recently from e734d34 to b816796 Compare May 4, 2021 23:33
@renovate-bot renovate-bot force-pushed the renovate/gradle-7.x branch 2 times, most recently from 460fe65 to b1a6c08 Compare May 14, 2021 15:31
@Neenu1995 Neenu1995 added the automerge Merge the pull request once unit tests and other checks pass. label May 31, 2021
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

1 similar comment
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jun 1, 2021
@Neenu1995 Neenu1995 added the automerge Merge the pull request once unit tests and other checks pass. label Jun 2, 2021
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

1 similar comment
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jun 3, 2021
@snippet-bot
Copy link

snippet-bot bot commented Jun 11, 2021

No region tags are edited in this PR.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@renovate-bot renovate-bot force-pushed the renovate/gradle-7.x branch 2 times, most recently from 369c27f to 95d3c88 Compare June 14, 2021 16:05
@trusted-contributions-gcf trusted-contributions-gcf bot added the owlbot:run Add this label to trigger the Owlbot post processor. label Jul 2, 2021
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Jul 2, 2021
@Neenu1995 Neenu1995 added the automerge Merge the pull request once unit tests and other checks pass. label Jul 2, 2021
@eaball35 eaball35 added the automerge Merge the pull request once unit tests and other checks pass. label Sep 13, 2021
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Sep 13, 2021
@lesv lesv added the automerge Merge the pull request once unit tests and other checks pass. label Sep 20, 2021
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Sep 21, 2021
@lesv lesv added the automerge Merge the pull request once unit tests and other checks pass. label Sep 24, 2021
@lesv lesv added kokoro:force-run Add this label to force Kokoro to re-run the tests. and removed kokoro:force-run Add this label to force Kokoro to re-run the tests. labels Sep 24, 2021
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Sep 25, 2021
@meltsufin meltsufin added the automerge Merge the pull request once unit tests and other checks pass. label Sep 29, 2021
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Sep 29, 2021
@meltsufin meltsufin added the automerge Merge the pull request once unit tests and other checks pass. label Oct 1, 2021
@gcf-merge-on-green
Copy link
Contributor

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Oct 1, 2021
@chanseokoh chanseokoh added the automerge Merge the pull request once unit tests and other checks pass. label Oct 7, 2021
@chanseokoh chanseokoh closed this Oct 7, 2021
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Oct 7, 2021
@forking-renovate
Copy link

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 7.x releases. However, if you upgrade to 7.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@renovate-bot renovate-bot deleted the renovate/gradle-7.x branch October 7, 2021 20:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes This human has signed the Contributor License Agreement. kokoro:force-run Add this label to force Kokoro to re-run the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants