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
discard dbbb59872a Minor: Regenerated BOMs for
12cdbc9e2889961d65cbf33655911bc9a61cb6b6
add 26277e85f5 [tomee-10.x]: Bump version.hibernate.orm (#2809)
add 9448db5586 Minor: Regenerated BOMs for
26277e85f5f7a623fdd5f19d2d2cee24ef4a7b43
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 (dbbb59872a)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (9448db5586)
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(-)
