This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a change to branch maven4-enabled
in repository https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git
discard dd96008 work around Maven 4 CLI lack of interpolation
discard f3a642f enable build with Maven 4
add c4f68d3 Bump org.apache.maven.plugins:maven-plugins from 48 to 49
add c89e957 Add AGENTS.md + SECURITY.md security-model pointer for
scanner discoverability
add 94ff81f Bump
apache/maven-gh-actions-shared/.github/workflows/pr-automation.yml (#680)
add b330006 Bump
apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml (#679)
add 0f52ee5 enable build with Maven 4
add 53ddb96 work around Maven 4 CLI lack of interpolation
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 (dd96008)
\
N -- N -- N refs/heads/maven4-enabled (53ddb96)
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 | 3 +-
.github/workflows/pr-automation.yml | 2 +-
.../src/main/webapp/WEB-INF/web.xml => AGENTS.md | 22 +++++---
.../path/to/pom.xml => SECURITY.md | 63 +++++++++++-----------
pom.xml | 2 +-
5 files changed, 49 insertions(+), 43 deletions(-)
copy src/it/mdeploy-45-test/src/main/webapp/WEB-INF/web.xml => AGENTS.md (65%)
copy src/it/MDEPLOY-184_deployfile-with-javadoc-and-sources/path/to/pom.xml =>
SECURITY.md (57%)
