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 c88370b359 Minor: Regenerated BOMs for
580dfe08d09b6090328df91bed58283fdbb6551e
omit 580dfe08d0 [tomee-10.x]: Bump org.codehaus.plexus:plexus-classworlds
from 2.12.0 to 2.12.1 (#3036)
add bedff626fb Minor: Regenerated BOMs for
943fc8527fe34b3bd7656733ae6df7439fb36e9e
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 (c88370b359)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (bedff626fb)
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:
itests/failover/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
