This is an automated email from the ASF dual-hosted git repository.
github-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 81f5b154ab Minor: Regenerated BOMs for
39ffe87adcca722e83f234147cfbbf08dffd91f9
add 1c9b8add2a [tomee-10.x]: Bump org.projectlombok:lombok from 1.18.42 to
1.18.44
add a0cb8fdfca [tomee-10.x]: Bump org.ehcache:ehcache from 3.11.1 to 3.12.0
add 6b32f92d55 Minor: Regenerated BOMs for
a0cb8fdfcaf18812b64eac2ef895ebe9e81455b0
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 (81f5b154ab)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (6b32f92d55)
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 +-
tomee/apache-tomee/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
