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 a6d7c28ea8 Minor: Regenerated BOMs for
e4a2caef3c544b761c21664ba07064e4f691154e
omit e4a2caef3c [tomee-10.x]: Bump org.bouncycastle:bcmail-jdk18on from
1.85 to 1.86 (#3034)
add acab71d3ba Minor: Regenerated BOMs for
6b0d3bc975cc38ed72f1fda247464882ff79a437
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 (a6d7c28ea8)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (acab71d3ba)
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:
server/openejb-client/pom.xml | 2 +-
tomee/tomee-embedded/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
