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
omit 219ebc2fef Minor: Regenerated BOMs for
d24fc1b00b6a867a442efd648c18c6c03c4b2b12
add ca702739d3 TOMEE-4363 - DBCP 2.12.0
add ca7cf25450 Minor: Regenerated BOMs for
ca702739d3180a991b1981e7b51465afff9e7609
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 (219ebc2fef)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(ca7cf25450)
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(-)
