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
discard 8320e6c38e Minor: Regenerated BOMs for
8a02dd5dc7fa71b293e3b906cda3b98c3f1babf4
add df37ac316c Bump version.log4j2 from 2.25.2 to 2.25.3
add 7d5cfb6f3d Bump version.spring-boot from 4.0.0 to 4.0.1
add 3eeaa21138 Minor: Regenerated BOMs for
7d5cfb6f3d749a83c09a13ead9e5b86e1e7bbc67
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 (8320e6c38e)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(3eeaa21138)
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:
arquillian/functional-tests/spring-cxf-tomee-4332/pom.xml | 2 +-
pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
