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_tomee-10.x
in repository https://gitbox.apache.org/repos/asf/tomee.git
omit 2af52e6be7 Minor: Regenerated BOMs for
3d05d87148ccd5808e76a874ce638e27b0e5fc80
add f60024447c TOMEE-4637 - Bump version.jackson from 2.22.0 to 2.22.1
(#2829)
add cf5aee7399 Minor: Regenerated BOMs for
f60024447c54c28174d0cfa03732565242e185aa
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 (2af52e6be7)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (cf5aee7399)
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(-)
