This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 29843ab670 Minor: Regenerated BOMs for
a7999b17e4a4bb03c9379d0e10737f6a2b3f3a9a
add a40aeebcde Bump commons-io:commons-io from 2.21.0 to 2.22.0
add e4915f3afe Minor: Regenerated BOMs for
a40aeebcde5ac4d328663de22d9201d572fab251
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 (29843ab670)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(e4915f3afe)
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(-)
