This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch regenerate_boms_after_dep_upgrade in repository https://gitbox.apache.org/repos/asf/tomee.git
omit 01ca3c9257 Minor: Regenerated BOMs for 35d837c5f3f0d0ff313526fcf64799e6d3dfdea5 add 75ec55cb2b Align with TomEE 9.x version by removing unnecessary excludes add 67addc60d4 Minor: Regenerated BOMs for 75ec55cb2b2cbc2ff2476989cda5adac07531a30 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 (01ca3c9257) \ N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade (67addc60d4) 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: tomee/tomee-microprofile/mp-common/pom.xml | 10 ---------- 1 file changed, 10 deletions(-)