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 81f6d1e4b3 Minor: Regenerated BOMs for
268f1e6f3f0974f17650f171df81ce43f1c4914c
add 76f206ddc6 [tomee-10.x]: Bump net.bytebuddy:byte-buddy from 1.18.2 to
1.18.3
add 1360ef01b5 [tomee-10.x]: Bump org.codehaus.mojo:exec-maven-plugin
add 439831b11c Minor: Regenerated BOMs for
1360ef01b566a683f18ba1c6e0fd409f99865e15
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 (81f6d1e4b3)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (439831b11c)
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 +-
pom.xml | 2 +-
tck/cdi-tomee/pom.xml | 2 +-
tomee/apache-tomee/pom.xml | 4 ++--
4 files changed, 5 insertions(+), 5 deletions(-)
