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 a4a4aab824 Minor: Regenerated BOMs for
6b749c4f44dc3b7320636f333cea9835fff9ad28
add 3f48650d2b [tomee-10.x]: Bump
org.apache.maven.plugins:maven-compiler-plugin from 3.15.0 to 3.16.0 (#3042)
add 4fcc7b6065 Minor: Regenerated BOMs for
3f48650d2bf46fe304a27231d70b06dc8a5d1a3c
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 (a4a4aab824)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (4fcc7b6065)
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 | 2 +-
tck/concurrency-standalone/pom.xml | 2 +-
tomee/apache-tomee/pom.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
