This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch mvn363x
in repository https://gitbox.apache.org/repos/asf/maven-archiver.git
discard 71579ac goal change
discard fab632c Check with mvn 3.9 and 4
discard 412b73c Bump to Maven 3.9.12
discard cd0663c drop comments
discard 358923d Bump Maven to 3.6.3
add 4c7c849 Bump Maven to 3.9.12
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 (71579ac)
\
N -- N -- N refs/heads/mvn363x (4c7c849)
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 | 4 +---
pom.xml | 10 ----------
2 files changed, 1 insertion(+), 13 deletions(-)
