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 00b8e09db2 Minor: Regenerated BOMs for
d60a85166af1995d55517bc75a6bcfff64697a6d
add 9965045eb7 Bump version.jackson from 2.21.1 to 2.21.2
add 2665861672 Minor: Regenerated BOMs for
9965045eb79c0b2c8790d446989fb6dc75c18ebf
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 (00b8e09db2)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(2665861672)
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:
boms/tomee-microprofile/pom.xml | 6 +++---
boms/tomee-plume/pom.xml | 6 +++---
boms/tomee-plus/pom.xml | 6 +++---
pom.xml | 2 +-
4 files changed, 10 insertions(+), 10 deletions(-)
