This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard a42d92d2b5 Minor: Regenerated BOMs for
4a8b75ad2c16be7e614251e7d75e3f05661d85ef
add eb0d69635c Bump com.github.tomakehurst:wiremock from 2.10.1 to 2.27.2
add 10ea86762f Bump org.htmlunit:htmlunit from 3.5.0 to 4.4.0 in /examples
add 46a8a45f78 Minor: Regenerated BOMs for
10ea86762f86eb7ae446d9789fc481859084f709
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 (a42d92d2b5)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(46a8a45f78)
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:
examples/security-openid/pom.xml | 2 +-
tck/microprofile-tck/rest-client/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
