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 5fdb42cd85 Minor: Regenerated BOMs for
548155f1ab0b8e070b2cbc37790beb99ae13332e
add 265a818eb4 [tomee-10.x]: Bump version.hibernate.orm
new 7c63003a2e Minor: Regenerated BOMs for
265a818eb4c59a99cdf9d0645972aec71a2289ba
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 (5fdb42cd85)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (7c63003a2e)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
