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_tomee-10.x
in repository https://gitbox.apache.org/repos/asf/tomee.git
omit f07ad580dd Minor: Regenerated BOMs for
6c9415c534ddc8815245d38af87bd4beb38e3fac
add ff70f30de8 [tomee-10.x]: Bump org.apache:apache from 37 to 38
add bed902fe84 Minor: Regenerated BOMs for
ff70f30de832495fcb41c4fc21e91232ca260260
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 (f07ad580dd)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (bed902fe84)
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(-)
