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 a815730de8 Minor: Regenerated BOMs for
f4e755d30e2b66b82d62305b69ea8e834d60ec99
add bd066db57a [tomee-10.x]: Bump org.codehaus.plexus:plexus-archiver from
4.14.0 to 4.15.0 (#3129)
add c5b27f8618 Minor: Regenerated BOMs for
bd066db57ae08af566af625855d28114465bb4d3
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 (a815730de8)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (c5b27f8618)
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(-)
