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
discard 9ad7065ac3 Minor: Regenerated BOMs for
a0e17ac930321961111ff410add7e819d33b9ed0
add 875e7b9958 TOMEE-4723 - Jackson 2.22.3 (#3010)
add 43f5fc9fcb Minor: Regenerated BOMs for
875e7b9958ce210f643250af1859a8ef5f52d92b
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 (9ad7065ac3)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(43f5fc9fcb)
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(-)
