build(deps): bump com.googlecode.libphonenumber:libphonenumber from 9.0.36 to 9.0.37 in the libphonenumber group - #1259
Conversation
Bumps the libphonenumber group with 1 update: [com.googlecode.libphonenumber:libphonenumber](https://github.com/google/libphonenumber). Updates `com.googlecode.libphonenumber:libphonenumber` from 9.0.36 to 9.0.37 - [Release notes](https://github.com/google/libphonenumber/releases) - [Changelog](https://github.com/google/libphonenumber/blob/master/release_notes.txt) - [Commits](google/libphonenumber@v9.0.36...v9.0.37) --- updated-dependencies: - dependency-name: com.googlecode.libphonenumber:libphonenumber dependency-version: 9.0.37 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: libphonenumber ... Signed-off-by: dependabot[bot] <support@github.com>
|
Holding this one. That skew is what PR #1258 just fixed, and why the two are pinned together with a note in The grouping added in #1258 is working as intended — this arrived as a group PR. It just happens to contain only one artifact, because the port hasn't caught up. The port sets the ceiling; we bump @dependabot ignore this patch version |
|
@dependabot ignore com.googlecode.libphonenumber:libphonenumber this version |
|
Closing manually — Dependabot didn't act on the |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the libphonenumber group with 1 update: com.googlecode.libphonenumber:libphonenumber.
Updates
com.googlecode.libphonenumber:libphonenumberfrom 9.0.36 to 9.0.37Release notes
Sourced from com.googlecode.libphonenumber:libphonenumber's releases.
Changelog
Sourced from com.googlecode.libphonenumber:libphonenumber's changelog.
... (truncated)
Commits
b232be1[maven-release-plugin] prepare release v9.0.37c9d5f73Metadata updates for release 9.0.37 (#4064)2b03a90Rnidhi maven update6 (#4045)f6f65e1Update README.md (#4046)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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions