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 ee73bd2bbb Minor: Regenerated BOMs for
c9a03fa615ac7f8199e120186232010fc73aeef6
add c911d9b6dd [tomee-10.x]: Bump maven.version from 3.9.16 to 3.10.0
(#3019)
add 7b6f87f151 Minor: Regenerated BOMs for
c911d9b6dd0700302c410c7f0f752e23956ff0df
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 (ee73bd2bbb)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (7b6f87f151)
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:
maven/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
