This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 0f3be62067 Minor: Regenerated BOMs for
a0346ac309df316a9c488d9ad12a8af5eddd0028
add de50ddb492 Bump version.log4j2 from 2.25.3 to 2.25.4
add 5cb8dfdb01 Minor: Regenerated BOMs for
de50ddb492aa6c22c4574f14f43860a091dfc0ff
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 (0f3be62067)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(5cb8dfdb01)
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:
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
