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 4f24ab2aeb Minor: Regenerated BOMs for
631afbfc793e3190756ce599d788c871a4846c51
add 871c5d6879 Bump org.apache.maven:maven-archiver from 3.6.5 to 3.6.6
add 6e95e5fc69 Minor: Regenerated BOMs for
871c5d68792857d3592b6494c62f8bbc2d2d4e38
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 (4f24ab2aeb)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(6e95e5fc69)
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:
maven/applicationcomposer-maven-plugin/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
