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 2fb36203ef Minor: Regenerated BOMs for
7bc544a9c65b3e28889f0ce2efda841504830914
add 9ac974aa75 Bump org.ow2.asm:asm-util from 9.9.1 to 9.10.1
add 83170aadf1 Minor: Regenerated BOMs for
9ac974aa75b7bc2d353c9922d0b3b2032296e0bb
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 (2fb36203ef)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(83170aadf1)
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:
mp-jwt/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
