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 2adbe1c7a2 Minor: Regenerated BOMs for
2ecbdd9e79cdc6d52f7fac05bafb42de90526c28
add 88c5bd6ab9 [tomee-10.x]: Bump version.shrinkwrap.resolver.bom from
3.3.5 to 3.3.7
add 9d830c30f5 Minor: Regenerated BOMs for
88c5bd6ab9c6aa3265a8d905602131c88a9e2338
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 (2adbe1c7a2)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (9d830c30f5)
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(-)
