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 7ac02c5f86 Minor: Regenerated BOMs for
119209300253e817b6bb6c2b49b68560466aa946
add 615fdb57d8 [tomee-10.x]: Bump
org.apache.maven.plugins:maven-failsafe-plugin from 3.6.0 to 3.6.1 (#3140)
add 23d0850da7 Minor: Regenerated BOMs for
615fdb57d837e3d246c2fda370c646b653c74647
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 (7ac02c5f86)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (23d0850da7)
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 +-
1 file changed, 1 insertion(+), 1 deletion(-)