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 779ea66957 Minor: Regenerated BOMs for
b2bc764be3a6d6c1596f7d380c6a67e5558d79d9
add 7fc3fa58ed Bump org.apache.sshd:sshd-core from 2.17.1 to 2.18.0
add 0c0212986e Minor: Regenerated BOMs for
7fc3fa58ed27b21e7c988b61acc86fe5a3e41fd5
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 (779ea66957)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(0c0212986e)
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(-)
