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 a6d0662eb1 Minor: Regenerated BOMs for
a82f28d326fa6554564cc5dc02a3bee5948e980b
add 268f1e6f3f [tomee-10.x]: Bump org.apache.maven:maven-archiver from
3.6.5 to 3.6.6
add 76f206ddc6 [tomee-10.x]: Bump net.bytebuddy:byte-buddy from 1.18.2 to
1.18.3
add aa29b5db8b Minor: Regenerated BOMs for
76f206ddc642b0c2ca512a4f20d575e74a0ef608
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 (a6d0662eb1)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (aa29b5db8b)
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:
arquillian/arquillian-tomee-tests/pom.xml | 2 +-
maven/applicationcomposer-maven-plugin/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
