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-release.git
omit b88a09e7 Bump mavenVersion from 3.9.16 to 3.10.0
add 90d44007 Update ATR metadata [ci skip]
add a6de910f Use push for PR Automation and add PR Check (#1522)
add 4fb21fc9 Ignore SLF4J 2.x in Dependabot
add ae427693 Bump org.eclipse.sisu:org.eclipse.sisu.inject from 1.1.0 to
1.1.1 (#1526)
add 27a6ec56 Bump org.eclipse.sisu:org.eclipse.sisu.plexus from 1.1.0 to
1.1.1 (#1525)
add d831d20d Align Resolver with Maven 3.9.16
add 85f57d12 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 (b88a09e7)
\
N -- N -- N refs/heads/dependabot/maven/mavenVersion-3.10.0
(85f57d12)
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 | 32 ++++++++++++++++++++++
.github/dependabot.yml | 3 ++
.github/workflows/pr-automation.yml | 6 ++--
.github/workflows/{stale.yml => pr-check.yml} | 13 ++++-----
.../workflows/{maven-verify.yml => pr-signal.yml} | 18 +++++++-----
maven-release-plugin/pom.xml | 4 +--
pom.xml | 2 +-
7 files changed, 58 insertions(+), 20 deletions(-)
copy .github/workflows/{stale.yml => pr-check.yml} (82%)
copy .github/workflows/{maven-verify.yml => pr-signal.yml} (74%)
