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 439831b11c Minor: Regenerated BOMs for
1360ef01b566a683f18ba1c6e0fd409f99865e15
add b141e92eec [tomee-10.x]: Bump version.hibernate.orm
add 1ef68fb2f4 Minor: Regenerated BOMs for
b141e92eec56dec8e288ac7c7e73aea40fb07bdb
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 (439831b11c)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (1ef68fb2f4)
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(-)
