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
omit 0419f75ee0 Minor: Regenerated BOMs for
df67cf968f1ca19352c9fc6441f12997c52cf08c
add a078ac7508 Bump io.cucumber:cucumber-java from 7.30.0 to 7.31.0
add 18102b7a82 Minor: Regenerated BOMs for
63ccec6235831b941e5331e159d47dc0a6051d5c
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 (0419f75ee0)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(18102b7a82)
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:
examples/cucumber-jvm/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
