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 b34777ea79 Minor: Regenerated BOMs for
6e34fdb57aa4e8ab507f3c0bdd67ae72f76c2896
add 25011b5ec8 Bump org.codehaus.plexus:plexus-classworlds from 2.9.0 to
2.12.0
add fd58205a88 Minor: Regenerated BOMs for
25011b5ec8423bc1109abfe84b9161e19f729eac
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 (b34777ea79)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(fd58205a88)
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(-)
