[PR] build(deps): bump com.google.guava:guava from 33.1.0-jre to 33.2.1-jre [myfaces-tobago]
dependabot[bot] opened a new pull request, #5193: URL: https://github.com/apache/myfaces-tobago/pull/5193 Bumps [com.google.guava:guava](https://github.com/google/guava) from 33.1.0-jre to 33.2.1-jre. Release notes Sourced from https://github.com/google/guava/releases;>com.google.guava:guava's releases. 33.2.1 dependency groupIdcom.google.guava/groupId artifactIdguava/artifactId version33.2.1-jre/version !-- or, for Android: -- version33.2.1-android/version /dependency Jar files https://repo1.maven.org/maven2/com/google/guava/guava/33.2.1-jre/guava-33.2.1-jre.jar;>33.2.1-jre.jar https://repo1.maven.org/maven2/com/google/guava/guava/33.2.1-android/guava-33.2.1-android.jar;>33.2.1-android.jar Guava requires https://github.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies;>one runtime dependency, which you can download here: https://repo1.maven.org/maven2/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar;>failureaccess-1.0.1.jar Javadoc https://guava.dev/releases/33.2.1-jre/api/docs/;>33.2.1-jre https://guava.dev/releases/33.2.1-android/api/docs/;>33.2.1-android JDiff https://guava.dev/releases/33.2.1-jre/api/diffs/;>33.2.1-jre vs. 33.2.0-jre https://guava.dev/releases/33.2.1-android/api/diffs/;>33.2.1-android vs. 33.2.0-android https://guava.dev/releases/33.2.1-android/api/androiddiffs/;>33.2.1-android vs. 33.2.1-jre Changelog net: Changed InetAddress-String conversion methods to preserve the IPv6 scope ID if present. The scope ID can be necessary for IPv6-capable devices with multiple network interfaces. However, preserving it can also lead to problems for callers that rely on the returned values not to include the scope ID: Callers might compensate for the old behavior of the methods by appending the scope ID to a returned string themselves. If so, you can update your code to stop doing so at the same time as you upgrade Guava. Of, if your code might run against multiple versions of Guava, you can check whether Guava has included a scope ID before you add one yourself. Callers might pass the returned string to another system that does not understand scope IDs. If so, you can strip the scope ID off, whether by truncating the string form at a % character (leaving behind any trailing ] character in the case of forUriString) or by replacing the returned InetAddress with a new instance constructed by calling InetAddress.getByAddress(addr). java.net.InetAddress validates any provided scope ID against the interfaces available on the machine. As a result, methods in InetAddresses may now fail if the scope ID fails validation. Notable cases in which this may happen include: if the code runs in an Android app without networking permission if code passes InetAddress instances or strings across devices If this is not the behavior that you want, then you can strip off the scope ID from the input string before passing it to Guava, as discussed above. (3f61870ac6) 33.2.0 Android users: Please test recent Guava versions If you know of Guava Android users who have not yet upgraded to at least release https://github.com/google/guava/releases/tag/v33.0.0;>33.0.0, please encourage them to upgrade, preferably to today's release, 33.2.0. These releases have begun adding Java 8+ APIs to guava-android. While we don't anticipate problems, we do anticipate that any unexpected problems could force a disruptive rollback. To minimize any disruption, we'd like to catch any such problems early. Please https://github.com/google/guava/issues/new?assignees=labels=type%3Ddefectprojects=template=bug_report.yaml;>let us know of any problems you encounter. Maven ... (truncated) Commits See full diff in https://github.com/google/guava/commits;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- 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
Re: [PR] build(deps): bump com.google.guava:guava from 33.1.0-jre to 33.2.1-jre [myfaces-tobago]
bohmber merged PR #5157: URL: https://github.com/apache/myfaces-tobago/pull/5157 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@myfaces.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] build(deps): bump com.google.guava:guava from 33.1.0-jre to 33.2.1-jre [myfaces-tobago]
bohmber merged PR #5150: URL: https://github.com/apache/myfaces-tobago/pull/5150 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@myfaces.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] build(deps): bump com.google.guava:guava from 33.1.0-jre to 33.2.1-jre [myfaces-tobago]
dependabot[bot] opened a new pull request, #5157: URL: https://github.com/apache/myfaces-tobago/pull/5157 Bumps [com.google.guava:guava](https://github.com/google/guava) from 33.1.0-jre to 33.2.1-jre. Release notes Sourced from https://github.com/google/guava/releases;>com.google.guava:guava's releases. 33.2.1 dependency groupIdcom.google.guava/groupId artifactIdguava/artifactId version33.2.1-jre/version !-- or, for Android: -- version33.2.1-android/version /dependency Jar files https://repo1.maven.org/maven2/com/google/guava/guava/33.2.1-jre/guava-33.2.1-jre.jar;>33.2.1-jre.jar https://repo1.maven.org/maven2/com/google/guava/guava/33.2.1-android/guava-33.2.1-android.jar;>33.2.1-android.jar Guava requires https://github.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies;>one runtime dependency, which you can download here: https://repo1.maven.org/maven2/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar;>failureaccess-1.0.1.jar Javadoc https://guava.dev/releases/33.2.1-jre/api/docs/;>33.2.1-jre https://guava.dev/releases/33.2.1-android/api/docs/;>33.2.1-android JDiff https://guava.dev/releases/33.2.1-jre/api/diffs/;>33.2.1-jre vs. 33.2.0-jre https://guava.dev/releases/33.2.1-android/api/diffs/;>33.2.1-android vs. 33.2.0-android https://guava.dev/releases/33.2.1-android/api/androiddiffs/;>33.2.1-android vs. 33.2.1-jre Changelog net: Changed InetAddress-String conversion methods to preserve the IPv6 scope ID if present. The scope ID can be necessary for IPv6-capable devices with multiple network interfaces. However, preserving it can also lead to problems for callers that rely on the returned values not to include the scope ID: Callers might compensate for the old behavior of the methods by appending the scope ID to a returned string themselves. If so, you can update your code to stop doing so at the same time as you upgrade Guava. Of, if your code might run against multiple versions of Guava, you can check whether Guava has included a scope ID before you add one yourself. Callers might pass the returned string to another system that does not understand scope IDs. If so, you can strip the scope ID off, whether by truncating the string form at a % character (leaving behind any trailing ] character in the case of forUriString) or by replacing the returned InetAddress with a new instance constructed by calling InetAddress.getByAddress(addr). java.net.InetAddress validates any provided scope ID against the interfaces available on the machine. As a result, methods in InetAddresses may now fail if the scope ID fails validation. Notable cases in which this may happen include: if the code runs in an Android app without networking permission if code passes InetAddress instances or strings across devices If this is not the behavior that you want, then you can strip off the scope ID from the input string before passing it to Guava, as discussed above. (3f61870ac6) 33.2.0 Android users: Please test recent Guava versions If you know of Guava Android users who have not yet upgraded to at least release https://github.com/google/guava/releases/tag/v33.0.0;>33.0.0, please encourage them to upgrade, preferably to today's release, 33.2.0. These releases have begun adding Java 8+ APIs to guava-android. While we don't anticipate problems, we do anticipate that any unexpected problems could force a disruptive rollback. To minimize any disruption, we'd like to catch any such problems early. Please https://github.com/google/guava/issues/new?assignees=labels=type%3Ddefectprojects=template=bug_report.yaml;>let us know of any problems you encounter. Maven ... (truncated) Commits See full diff in https://github.com/google/guava/commits;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- 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
[PR] build(deps): bump com.google.guava:guava from 33.1.0-jre to 33.2.1-jre [myfaces-tobago]
dependabot[bot] opened a new pull request, #5150: URL: https://github.com/apache/myfaces-tobago/pull/5150 Bumps [com.google.guava:guava](https://github.com/google/guava) from 33.1.0-jre to 33.2.1-jre. Release notes Sourced from https://github.com/google/guava/releases;>com.google.guava:guava's releases. 33.2.1 dependency groupIdcom.google.guava/groupId artifactIdguava/artifactId version33.2.1-jre/version !-- or, for Android: -- version33.2.1-android/version /dependency Jar files https://repo1.maven.org/maven2/com/google/guava/guava/33.2.1-jre/guava-33.2.1-jre.jar;>33.2.1-jre.jar https://repo1.maven.org/maven2/com/google/guava/guava/33.2.1-android/guava-33.2.1-android.jar;>33.2.1-android.jar Guava requires https://github.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies;>one runtime dependency, which you can download here: https://repo1.maven.org/maven2/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar;>failureaccess-1.0.1.jar Javadoc https://guava.dev/releases/33.2.1-jre/api/docs/;>33.2.1-jre https://guava.dev/releases/33.2.1-android/api/docs/;>33.2.1-android JDiff https://guava.dev/releases/33.2.1-jre/api/diffs/;>33.2.1-jre vs. 33.2.0-jre https://guava.dev/releases/33.2.1-android/api/diffs/;>33.2.1-android vs. 33.2.0-android https://guava.dev/releases/33.2.1-android/api/androiddiffs/;>33.2.1-android vs. 33.2.1-jre Changelog net: Changed InetAddress-String conversion methods to preserve the IPv6 scope ID if present. The scope ID can be necessary for IPv6-capable devices with multiple network interfaces. However, preserving it can also lead to problems for callers that rely on the returned values not to include the scope ID: Callers might compensate for the old behavior of the methods by appending the scope ID to a returned string themselves. If so, you can update your code to stop doing so at the same time as you upgrade Guava. Of, if your code might run against multiple versions of Guava, you can check whether Guava has included a scope ID before you add one yourself. Callers might pass the returned string to another system that does not understand scope IDs. If so, you can strip the scope ID off, whether by truncating the string form at a % character (leaving behind any trailing ] character in the case of forUriString) or by replacing the returned InetAddress with a new instance constructed by calling InetAddress.getByAddress(addr). java.net.InetAddress validates any provided scope ID against the interfaces available on the machine. As a result, methods in InetAddresses may now fail if the scope ID fails validation. Notable cases in which this may happen include: if the code runs in an Android app without networking permission if code passes InetAddress instances or strings across devices If this is not the behavior that you want, then you can strip off the scope ID from the input string before passing it to Guava, as discussed above. (3f61870ac6) 33.2.0 Android users: Please test recent Guava versions If you know of Guava Android users who have not yet upgraded to at least release https://github.com/google/guava/releases/tag/v33.0.0;>33.0.0, please encourage them to upgrade, preferably to today's release, 33.2.0. These releases have begun adding Java 8+ APIs to guava-android. While we don't anticipate problems, we do anticipate that any unexpected problems could force a disruptive rollback. To minimize any disruption, we'd like to catch any such problems early. Please https://github.com/google/guava/issues/new?assignees=labels=type%3Ddefectprojects=template=bug_report.yaml;>let us know of any problems you encounter. Maven ... (truncated) Commits See full diff in https://github.com/google/guava/commits;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- 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
