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 eae378de39 Minor: Regenerated BOMs for
86f1fd435554e39b1dd39e4e2546a73c4a980f97
add 45998c20d2 Bump org.apache.sshd:sshd-core from 2.16.0 to 2.17.1
add 69a127f009 Minor: Regenerated BOMs for
45998c20d22c562f26421bf86e18d46bb0745154
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 (eae378de39)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(69a127f009)
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(-)
