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 af3a99a22e Minor: Regenerated BOMs for
df8e103c55d87711ab446923ad35574aec7a1468
add 97b54cc5c1 [tomee-10.x]: Bump com.nimbusds:nimbus-jose-jwt from 10.9.1
to 10.10 (#3001)
add c7abbd4b84 Minor: Regenerated BOMs for
97b54cc5c14f462215b30a2a3653b5e1fa0bcc39
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 (af3a99a22e)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (c7abbd4b84)
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(-)
