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 a231b53dea Minor: Regenerated BOMs for
1e64f66967af2f9ec90c3d7f4d38a5e6f8bdf9c9
add d69bf4d335 [tomee-10.x]: Bump org.apache.sshd:sshd-core from 2.17.1 to
2.18.0
add 3cdfb030ef Minor: Regenerated BOMs for
d69bf4d335b5a3701a9cf2b455d1ea3160e6867e
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 (a231b53dea)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (3cdfb030ef)
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(-)
