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
omit 3dda9df704 Minor: Regenerated BOMs for
24837fbf52490c17484c0e03116ed8557e99ac90
add 2e6dcb3e9e [tomee-10.x]: Bump
org.apache.maven.plugin-tools:maven-plugin-annotations from 3.15.2 to 3.16.0
(#2980)
add 36eb0f94c5 [tomee-10.x]: Bump org.apache:apache from 39 to 40 (#2969)
add 546f57975a [tomee-10.x]: Bump version.hibernate.orm from 6.6.56.Final
to 6.6.58.Final (#2985)
add 7e6bc0d3de Minor: Regenerated BOMs for
546f57975a276daa1782c5178a800e146255e9a3
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 (3dda9df704)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (7e6bc0d3de)
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 +-
pom.xml | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
