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
discard 6a1c4cd9d6 Minor: Regenerated BOMs for
bef5a48f25abeecaf967da69a93af968add76592
add 068bdcbfe3 Bump org.apache.maven.plugins:maven-compiler-plugin from
3.15.0 to 3.16.0 (#3041)
add e86cec3d5d Bump org.codehaus.mojo:build-helper-maven-plugin from 3.6.1
to 3.6.2 (#3055)
add 5ade615d67 Minor: Regenerated BOMs for
e86cec3d5d76dbc15b26edbf8ed8f005f1df313d
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 (6a1c4cd9d6)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(5ade615d67)
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:
deps/commons-dbcp2-shade/pom.xml | 2 +-
deps/taglibs-shade/pom.xml | 2 +-
pom.xml | 4 ++--
tomee/apache-tomee/pom.xml | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
