search

GoogleCloudPlatform / appengine-plugins

A client Java library to manage App Engine Java applications for any project that performs App Engine Java application management. For example, the Maven, Gradle and Eclipse App Engine plugins, custom user tools, etc.
Apache License 2.0
41 stars 27 forks source link

Bump com.google.cloud.tools:linkage-checker-enforcer-rules from 0.2.0 to 1.5.13 #960

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 11 months ago

Bumps com.google.cloud.tools:linkage-checker-enforcer-rules from 0.2.0 to 1.5.13.

Changelog

Sourced from com.google.cloud.tools:linkage-checker-enforcer-rules's changelog.

Linkage Checker Enforcer Rule and Linkage Monitor Change Log

1.5.12

  • Fixed the bug in the Gradle plugin that affected artifacts with "pom" packaging (#2196)

1.5.11

  • The Gradle plugin omits duplicate dependency paths when printing the locatin of problematic artifacts (#2188).

1.5.10

  • Fixed the bug that generated false positives on artifacts with classifiers (#2173)
  • Fixed the incorrect handling of protected methods on java.lang.Object (#2177)
  • The Gradle plugin shows partial results even if there are unexpected attributes of dependencies ( #2178).
  • The Gradle plugin checks circular dependencies when showing linkage errors (#2174).
  • The messages about linkage errors include the types of method and field symbols (2179).

1.5.9

  • Added an exclusion rule for invalid references in appengien-api-1.0-sdk (#2045)

1.5.8

  • Fixed the bug of the Linkage Checker enforcer rule not reporting failures when it cannot find exclusion files (#2006)
  • Updated the default exclusion rules with the classes referenced from Netty's optional features (#1977)

1.5.7

  • Fixed the problem of Linkage Monitor recognizing a parent pom as a BOM (#1958). Linkage Monitor now reads linkage-monitor-artifacts.txt for the list of artifacts generated by the repository.

1.5.6

  • Fixed false negative problem in Linkage Monitor where it did not find local artifacts listed in a BOM (#1919).

1.5.5

  • Linkage Monitor is part of the release process.

1.5.4

  • Fixed false positive linkage errors on unused private inner classes (#1608)

... (truncated)

Commits


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

gcf-merge-on-green[bot] commented 11 months ago

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.

dependabot[bot] commented 2 months ago

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 @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.