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 4b8641b505 Minor: Regenerated BOMs for
1bd07d01afe4f4d7bb443b0115a1aa46d36ff308
add 741c2a4d2e [tomee-10.x]: Bump
org.apache.maven.plugins:maven-deploy-plugin from 3.1.4 to 3.2.0 (#3007)
add 37264867f0 Minor: Regenerated BOMs for
741c2a4d2ecc0a0ffb9f702a88e0ae9cc6579435
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 (4b8641b505)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (37264867f0)
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(-)
