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 e0bc3e603b Minor: Regenerated BOMs for
758d6cdc8e0e6912033463cdfc5dc123fc6b1b13
add a7999b17e4 Bump actions/checkout from 6.0.2 to 6.0.3
new 29843ab670 Minor: Regenerated BOMs for
a7999b17e4a4bb03c9379d0e10737f6a2b3f3a9a
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 (e0bc3e603b)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(29843ab670)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/workflows/main-pull-request-build.yml | 2 +-
.github/workflows/main-push-build.yml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
