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 beb32c7431 Minor: Regenerated BOMs for
c60c973719b8c8bd8fb15c76543428a73d61fc45
omit c60c973719 Bump org.codehaus.plexus:plexus-archiver from 4.14.0 to
4.15.0 (#3128)
add efe3beabc2 Minor: Regenerated BOMs for
3abc86133791690b256c058674c44229350fc93d
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 (beb32c7431)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(efe3beabc2)
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:
pom.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
