This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/log4j-samples-graalvm/all-31eda36d8e
in repository https://gitbox.apache.org/repos/asf/logging-log4j-samples.git
discard 79d717d Bump the all group across 1 directory with 3 updates
add 85c4bf9 Bump graalvm/setup-graalvm from 1.3.4 to 1.3.5 in the all
group (#354)
add 9c6cb75 Bump com.android.application in the all group across 1
directory (#349)
add 66b3b1e Bump the all group across 1 directory with 3 updates
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 (79d717d)
\
N -- N -- N
refs/heads/dependabot/maven/log4j-samples-graalvm/all-31eda36d8e (66b3b1e)
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/graalvm-reusable-test.yaml | 2 +-
log4j-samples-android/app/build.gradle | 2 +-
log4j-samples-graalvm/pom.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
