This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/2.x/guava.version-33.3.0-jre in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard 965abfe93c Bump guava.version from 33.2.1-jre to 33.3.0-jre add 54924a416e Update `org.apache.maven.surefire:surefire-junit47` to version `3.4.0` (#2862) add 7a0057b8ea Update `org.apache.maven:maven-core` to version `3.9.9` (#2861) add 24b21b7e10 Update `commons-logging:commons-logging` to version `1.3.4` (#2864) add b911bffd0e Update `org.apache.commons:commons-compress` to version `1.27.1` (#2869) add a50366052a Update `com.google.guava:guava` to version `33.3.0-jre` (#2860) This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (965abfe93c) \ N -- N -- N refs/heads/dependabot/maven/2.x/guava.version-33.3.0-jre (a50366052a) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: log4j-parent/pom.xml | 8 ++++---- pom.xml | 4 ++-- src/changelog/.2.x.x/update_com_google_guava_guava.xml | 4 ++-- src/changelog/.2.x.x/update_commons_logging_commons_logging.xml | 4 ++-- .../.2.x.x/update_org_apache_commons_commons_compress.xml | 4 ++-- src/changelog/.2.x.x/update_org_apache_maven_maven_core.xml | 4 ++-- .../.2.x.x/update_org_apache_maven_surefire_surefire_junit47.xml | 4 ++-- 7 files changed, 16 insertions(+), 16 deletions(-)