This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/com.diffplug.spotless-spotless-maven-plugin-3.8.0
in repository https://gitbox.apache.org/repos/asf/maven-parent.git
discard 83cbc58 Bump com.diffplug.spotless:spotless-maven-plugin from 3.7.0
to 3.8.0
add 3177250 configure download_path_suffix for distribution area
add f5390e8 Bump
apache/maven-gh-actions-shared/.github/workflows/stale.yml (#584)
add bfdcfb4 Bump
apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml (#583)
add 710bf79 Bump
apache/maven-gh-actions-shared/.github/workflows/pr-automation.yml (#581)
add bb55156 Bump com.palantir.javaformat:palantir-java-format from 2.94.0
to 2.96.0
add 401673f Bump com.diffplug.spotless:spotless-maven-plugin from 3.7.0
to 3.8.0
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 (83cbc58)
\
N -- N -- N
refs/heads/dependabot/maven/com.diffplug.spotless-spotless-maven-plugin-3.8.0
(401673f)
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:
.asf.yaml | 1 +
.github/workflows/maven-verify.yml | 2 +-
.github/workflows/pr-automation.yml | 2 +-
.github/workflows/stale.yml | 2 +-
pom.xml | 2 +-
5 files changed, 5 insertions(+), 4 deletions(-)
