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
omit 8110107ff3 Minor: Regenerated BOMs for
15d3eb26c3b8257fd0912d3da04295e65612d9e8
omit 15d3eb26c3 [tomee-10.x]: Bump com.nimbusds:nimbus-jose-jwt from 10.8
to 10.9
add 398d94f589 Minor: Regenerated BOMs for
e956511b337725775dd9f78eaf98d4904098f7ca
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 (8110107ff3)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (398d94f589)
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 +-
tck/microprofile-tck/jwt/pom.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)