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
omit c378197f08 Minor: Regenerated BOMs for
d059a3ef619a6340d65f6f1f41ca1c0828a26330
add c34a063b92 Bump version.hibernate.orm from 7.4.2.Final to 7.4.3.Final
(#2810)
add 0c88a0cf1b Minor: Regenerated BOMs for
c34a063b92ae37040af618d6755da7e2d4f6d5c8
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 (c378197f08)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(0c88a0cf1b)
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(-)
