This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.resolver-maven-resolver-api-2.0.6
in repository https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git
discard 9c3a265 Bump org.apache.maven.resolver:maven-resolver-api from 2.0.2
to 2.0.6
add 76f0632 [MNGSITE-529] Rename "Goals" to "Plugin Documentation"
add 9410718 PR Automation only on close event
add 358ba26 Bump com.google.guava:guava from 33.2.1-jre to 33.4.0-jre
add 5ae9796 Upgrade dependencies to Maven 4.0.0-rc-2
add f55480e Bump org.apache.maven.resolver:maven-resolver-api from 2.0.2
to 2.0.6
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 (9c3a265)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.resolver-maven-resolver-api-2.0.6
(f55480e)
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:
.github/workflows/maven-verify.yml | 5 ++---
.github/workflows/pr-automation.yml | 2 --
pom.xml | 10 +++++-----
src/it/deploy-bom/verify.groovy | 2 +-
.../java/org/apache/maven/plugins/deploy/DeployFileMojo.java | 2 +-
src/main/java/org/apache/maven/plugins/deploy/DeployMojo.java | 7 ++++---
src/site/site.xml | 2 +-
.../maven/plugins/deploy/DeployMojoPomPackagingTest.java | 3 ++-
.../java/org/apache/maven/plugins/deploy/DeployMojoTest.java | 5 +++--
9 files changed, 19 insertions(+), 19 deletions(-)
