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 4fcc7b6065 Minor: Regenerated BOMs for
3f48650d2bf46fe304a27231d70b06dc8a5d1a3c
add 75c2b3eba6 [tomee-10.x]: Bump
org.codehaus.mojo:build-helper-maven-plugin from 3.6.1 to 3.6.2 (#3047)
add 1f9e1497c8 [tomee-10.x]: Bump org.apache.felix:maven-bundle-plugin
from 6.1.0 to 6.2.0 (#3039)
add cdcbff31b8 Minor: Regenerated BOMs for
1f9e1497c8d1bc2a797324d56e80a4c6d41ae70b
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 (4fcc7b6065)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (cdcbff31b8)
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 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
