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 aab661b87c Minor: Regenerated BOMs for
d76a3b13ee38827abbce3cef0db91776ae687281
add e956511b33 [tomee-10.x]: Bump version.hibernate.orm
add 15d3eb26c3 [tomee-10.x]: Bump com.nimbusds:nimbus-jose-jwt from 10.8
to 10.9
add 8110107ff3 Minor: Regenerated BOMs for
15d3eb26c3b8257fd0912d3da04295e65612d9e8
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 (aab661b87c)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (8110107ff3)
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:
itests/microprofile-jwt-itests/pom.xml | 2 +-
mp-jwt/pom.xml | 2 +-
pom.xml | 2 +-
tck/microprofile-tck/jwt/pom.xml | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
