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
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 4b5a377254 Minor: Regenerated BOMs for
985ae9648e4f6934d926da0dfad5d8fb9dd81e7f
add 954b87062f Bump org.ehcache:ehcache from 3.11.1 to 3.12.0
add 7b9d890d92 Minor: Regenerated BOMs for
954b87062feb15333088face550160e1f22bb7ef
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 (4b5a377254)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(7b9d890d92)
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(-)
