This is an automated email from the ASF dual-hosted git repository.
github-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 92340f480e Minor: Regenerated BOMs for
8467cfa82cb246558be69178e1e450109239ea00
add 9ed4f6ec56 Update create-pull-request action version
add 2da165d9c0 Minor: Regenerated BOMs for
f38ab4eac593cf4f55297a5e5abe1e659f7ca833
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 (92340f480e)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (2da165d9c0)
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:
.github/workflows/main-push-build.yml | 2 +-
boms/tomee-microprofile/pom.xml | 38 +++++++++++++++++------------------
boms/tomee-plume/pom.xml | 38 +++++++++++++++++------------------
boms/tomee-plus/pom.xml | 38 +++++++++++++++++------------------
boms/tomee-webprofile/pom.xml | 2 +-
5 files changed, 59 insertions(+), 59 deletions(-)
