This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/spring-boot.version-3.4.4
in repository https://gitbox.apache.org/repos/asf/logging-log4j-samples.git
omit 9ee0016 Bump spring-boot.version from 3.4.3 to 3.4.4
add aa5f3ef Pin transitive `joda-time` dependency
add 11e2ef8 Temporarily override Error Prone configuration
add e96f01b Update `joda-time:joda-time` to version `2.14.0` (#303)
add 74a4a6e Update `com.google.guava:guava` to version `33.4.7-jre` (#305)
add 058a21d Update `actions/setup-java` to version `4.7.1` (#307)
add f33da62 Add `.mvn/extensions.xml` to `.gitignore`
add 407c3a3 Bump org.apache.logging:logging-parent from 12.0.0 to 12.1.0
(#306)
add 1bedae2 Bump org.apache.logging:logging-parent from 12.0.0 to 12.1.0
in /log4j-samples-graalvm (#308)
add 56bf132 Update `graalvm/setup-graalvm` to version `1.3.3` (#288)
add 2ccdae2 Update `gradle/actions` to version `4.3.1` (#302)
add 0687a13 Bump spring-boot.version from 3.4.3 to 3.4.4
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 (9ee0016)
\
N -- N -- N
refs/heads/dependabot/maven/spring-boot.version-3.4.4 (0687a13)
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/android-reusable-test.yaml | 4 +-
.github/workflows/graalvm-reusable-test.yaml | 2 +-
.gitignore | 1 +
log4j-samples-graalvm/pom.xml | 23 ++++++++--
pom.xml | 64 ++++++++++++++++++++--------
5 files changed, 71 insertions(+), 23 deletions(-)
