This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch dependabot/maven/mavenVersion-3.10.0
in repository https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git
omit 1b66550 Bump mavenVersion from 3.9.16 to 3.10.0
add 5749cd1 Use push for PR Automation and add PR Check
add ba3fc36 Fix branch name in Release Drafter workflow
add e596ebb Restore Dependabot configuration after branch swap
add b901f69 Ignore SLF4J 2.x in Dependabot
add c458a0f Update ATR metadata
add d601e49 Require Maven 3.9.0
add e3e568a Point ciManagement at GitHub Actions
add 812b235 Remove redundant `javaVersion` property
add da6c94e Bump mavenVersion from 3.9.16 to 3.10.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 (1b66550)
\
N -- N -- N refs/heads/dependabot/maven/mavenVersion-3.10.0
(da6c94e)
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 | 13 +++++++++++--
.github/dependabot.yml | 21 +++++++++++++++++++++
.github/workflows/pr-automation.yml | 6 +++---
.github/workflows/{stale.yml => pr-check.yml} | 13 ++++++-------
.../workflows/{maven-verify.yml => pr-signal.yml} | 18 +++++++++++-------
.github/workflows/release-drafter.yml | 2 +-
pom.xml | 7 +++----
7 files changed, 56 insertions(+), 24 deletions(-)
copy .github/workflows/{stale.yml => pr-check.yml} (82%)
copy .github/workflows/{maven-verify.yml => pr-signal.yml} (74%)
