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
omit 2e5ff7adc5 Minor: Regenerated BOMs for
a13cfc90ab5b5657f06a7229764b9168edc8623f
omit a13cfc90ab [tomee-10.x]: Bump org.projectlombok:lombok from 1.18.46 to
1.18.48 (#3046)
add bb67ef7d63 Minor: Regenerated BOMs for
b239e88e3965973b244a6fd9a0f70a70f5a25e6e
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 (2e5ff7adc5)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (bb67ef7d63)
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/apache-tomee/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
