This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.plugins-maven-enforcer-plugin-3.0.0
in repository https://gitbox.apache.org/repos/asf/maven-script-interpreter.git.
discard 82e9099 Bump maven-enforcer-plugin from 3.0.0-M3 to 3.0.0
add e6a38f9 Update CI
add d317417 Bump actions/setup-java from 1 to 2.2.0
add 3c8ac05 Bump actions/cache from 2.1.5 to 2.1.6
add 900df19 Bump groovy from 2.4.20 to 2.4.21
add e357e1c Bump maven-javadoc-plugin from 3.2.0 to 3.3.1
add a56c150 Bump actions/setup-java from 2.2.0 to 2.3.1
add 9dfc181 [MSHARED-1001] Shared GitHub Actions (#55)
add 16667f1 Bump maven-enforcer-plugin from 3.0.0-M3 to 3.0.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 (82e9099)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.plugins-maven-enforcer-plugin-3.0.0
(16667f1)
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:
.../workflows/maven-verify.yml | 23 +++++++---
.github/workflows/maven.yml | 52 ----------------------
pom.xml | 4 +-
3 files changed, 18 insertions(+), 61 deletions(-)
copy src/site/resources/download.cgi => .github/workflows/maven-verify.yml
(74%)
delete mode 100644 .github/workflows/maven.yml
