[url_launcher]: Bump gradle from 3.4.2 to 4.2.0 in /packages/url_launcher/url_launcher_android/android #6580
Conversation
dependabot
bot
added
dependencies
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
Bumps gradle from 3.4.2 to 7.3.1. --- updated-dependencies: - dependency-name: com.android.tools.build:gradle dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/gradle/packages/url_launcher/url_launcher_android/android/com.android.tools.build-gradle-7.3.1
branch
from
7be731e to
67f24dc
Compare
GaryQian
changed the title
|
Performing a partial bump to 4.2.0 to avoid potential breakages. |
GaryQian
added
the
autosubmit
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/gradle/packages/url_launcher/url_launcher_android/android/com.android.tools.build-gradle-7.3.1
branch
…s/url_launcher/url_launcher_android/android (flutter/plugins#6580)
…s/url_launcher/url_launcher_android/android (flutter/plugins#6580)
…cher/url_launcher_android/android (flutter#6580)
…cher/url_launcher_android/android (flutter#6580)
2 participants
Bumps gradle from 3.4.2 to 7.3.1.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)