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
discard 43bf23366b Minor: Regenerated BOMs for
2b7c1e593ea337a967888a1649a6e1e5a1c34ebb
add 6a82244098 TOMEE-4664 - Bump org.apache.neethi:neethi from 3.2.2 to
3.2.3 (#2871)
add 3b6b59e2ac Minor: Regenerated BOMs for
6a822440981f4d843a26270ca00a72e618831be6
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 (43bf23366b)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (3b6b59e2ac)
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(-)
