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 87c7e5ae95 Minor: Regenerated BOMs for
bd542b8d4c61b4cd9b8655c976bf4652173cd1da
omit bd542b8d4c [tomee-10.x]: Bump org.codehaus.mojo:jaxb2-maven-plugin
from 4.1.0 to 4.2.0 (#3005)
add 82e6cad085 Minor: Regenerated BOMs for
308f5b8e0d49b30b11605abc39871b5711f8da94
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 (87c7e5ae95)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (82e6cad085)
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(-)
