This is an automated email from the ASF dual-hosted git repository.
github-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 6ec7f0b59c Minor: Regenerated BOMs for
6af3a477a0af891a9a7d9810fbae43437edd5009
add 1e36e407aa [tomee-10.x]: Bump org.codehaus.plexus:plexus-archiver
add 95b2e72566 Minor: Regenerated BOMs for
1e36e407aa91561d51bb20e48afa57a785d090d1
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 (6ec7f0b59c)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (95b2e72566)
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(-)
