This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/log4j2.version-2.19.0
in repository https://gitbox.apache.org/repos/asf/struts-examples.git
discard 10c6a38 Bump log4j2.version from 2.18.0 to 2.19.0
add 0991e66 Bump quarkus-plugin.version from 2.12.1.Final to 2.12.2.Final
add c2f58a0 Merge pull request #176 from
apache/dependabot/maven/quarkus-plugin.version-2.12.2.Final
add 05cc2df Bump log4j2.version from 2.18.0 to 2.19.0
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 (10c6a38)
\
N -- N -- N refs/heads/dependabot/maven/log4j2.version-2.19.0
(05cc2df)
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:
quarkus/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
