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 e59634c2f4 Minor: Regenerated BOMs for
58d247d292c86c9af4174c00381cdb953117745e
omit 58d247d292 Bump org.codehaus.gmavenplus:gmavenplus-plugin from 4.3.1
to 5.0.0
omit f475de258f Bump org.projectlombok:lombok from 1.18.42 to 1.18.46
add 6a07c9582e Minor: Regenerated BOMs for
59b457d0fd80f74e2f0ee531bf7bf257149f8012
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 (e59634c2f4)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(6a07c9582e)
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/apache-tomee/pom.xml | 2 +-
tomee/tomee-webaccess/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
