This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
regenerate_boms_after_dep_upgrade_tomee-10.x
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard bc4001d63e Minor: Regenerated BOMs for
c0262e4a20890ef16e61de4d68ff015a54722e15
add 37519fe865 TOMEE-4598 Bump commons-logging:commons-logging from 1.3.5
to 1.3.6 (#2591)
add 30e0ee2b9d Minor: Regenerated BOMs for
37519fe865644b6749cf19257ebb10575551df68
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 (bc4001d63e)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (30e0ee2b9d)
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 | 2 +-
boms/tomee-plume/pom.xml | 2 +-
boms/tomee-plus/pom.xml | 2 +-
boms/tomee-webprofile/pom.xml | 2 +-
pom.xml | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
