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
omit c7c4b8ec16 Minor: Regenerated BOMs for
b4867f607cb53cfc9e993a9cc671eaa7e72ae44d
add 2792f4a97b TOMEE-4627 - Bump commons-logging:commons-logging from
1.3.6 to 1.4.0 (#2766)
add 80dd43db6f Minor: Regenerated BOMs for
2792f4a97bd4ded543992ce02d5b1c0746b8e931
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 (c7c4b8ec16)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(80dd43db6f)
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(-)
