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 c8691b7e35 Minor: Regenerated BOMs for
2d021de9b676bf27a553ff10cc95ea9750d843ed
add 6f38f361f2 [tomee-10.x]: Bump org.codehaus.gmavenplus:gmavenplus-plugin
add d239fbbf65 Minor: Regenerated BOMs for
6f38f361f23c92f8c2d0394980774babf1014a8c
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 (c8691b7e35)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (d239fbbf65)
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:
tomee/tomee-webaccess/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
