(logging-log4j-samples) branch dependabot/maven/log4j-samples-graalvm/org.assertj-assertj-bom-3.26.3 updated (c3da23f -> 663d592)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/maven/log4j-samples-graalvm/org.assertj-assertj-bom-3.26.3
in repository https://gitbox.apache.org/repos/asf/logging-log4j-samples.git


 discard c3da23f  Bump org.assertj:assertj-bom in /log4j-samples-graalvm
     add db1dffd  Update `apache/logging-parent` to version `` (#172)
     add 1b2b9bc  Adapt to changes in `log4j-api` snapshot
     add dbf5b0d  Update Log4j to `2.24.0` (staging)
     add ad4a814  Update `org.yaml:snakeyaml` to version `2.3` (#175)
     add 34a16f3  Switch to RC2
     add 377ae9d  Update `org.eclipse.jetty:jetty-maven-plugin` to version `10.0.24` (#176)
     add 60f6af6  Upgrade to Log4j API 2.24.1-SNAPSHOT
     add c8a83c8  Update `ch.qos.logback:logback-classic` to version `1.5.8` (#178)
     add 8f0fd7f  Update `org.graalvm.buildtools:native-maven-plugin` to version `0.10.3` (#179)
     add 914fe60  Update `org.eclipse.jetty:jetty-maven-plugin` to version `11.0.0` (#181)
     add 992d58b  Update `org.eclipse.jetty:jetty-maven-plugin` to version `11.0.24` (#182)
     add b4e1d31  Update `apache/logging-parent` to version `` (#183)
     add 65fcacf  Update `org.apache.logging:logging-parent` to version `11.3.0` (#184)
     add ca937e1  Update `org.apache.logging:logging-parent` to version `11.3.0` (#185)
     add 3e5bbec  Update `com.google.guava:guava` to version `33.3.1-jre` (#186)
     add 3bfc988  Update to Log4j `2.24.1` RC1
     add 3ccde0f  Bump GraalVM test to `2.24.1`
     add f149fc7  Add repository
     add 471a7f3  Update `org.junit:junit-bom` to version `5.11.1` (#187)
     add 663d592  Bump org.assertj:assertj-bom in /log4j-samples-graalvm

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   (c3da23f)
            \
             N -- N -- N   refs/heads/dependabot/maven/log4j-samples-graalvm/org.assertj-assertj-bom-3.26.3 (663d592)

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:
 .github/workflows/build.yaml            |  2 +-
 .github/workflows/graalvm-test.yaml     |  2 +-
 .github/workflows/merge-dependabot.yaml |  4 ++--
 log4j-samples-graalvm/pom.xml           | 33 +++++++++++++++++++++++++++------
 pom.xml                                 | 33 +++++++++++++++++----------------
 5 files changed, 48 insertions(+), 26 deletions(-)