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 645024db2c Minor: Regenerated BOMs for
ef5637f11fc1ed61181ccc51d695bb7bb46df457
add 3d63c6cbb0 Revert "Bump org.openjdk.nashorn:nashorn-core from 15.4 to
15.5 (#1703)"
add fb02dfdc83 Minor: Regenerated BOMs for
3d63c6cbb0002d703d0d62489f782eb54d44a988
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 (645024db2c)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(fb02dfdc83)
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/testing-security-4/pom.xml | 2 +-
pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
