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
in repository https://gitbox.apache.org/repos/asf/tomee.git
omit 28dabc2c02 Minor: Regenerated BOMs for
61a47fd35f090708df9d7c71f00645e4422b0b1f
add 8d6900c174 Bump org.codehaus.mojo:exec-maven-plugin from 3.6.3 to
3.6.4 (#2974)
add 64a10d0301 Minor: Regenerated BOMs for
8d6900c174e5637e50759f0a400871e3b6f139ed
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 (28dabc2c02)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(64a10d0301)
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:
pom.xml | 2 +-
tck/cdi-tomee/pom.xml | 2 +-
tck/security-standalone/pom.xml | 2 +-
tomee/apache-tomee/pom.xml | 4 ++--
4 files changed, 5 insertions(+), 5 deletions(-)
