This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/maven-resolver-1.9.x/org.codehaus.plexus-plexus-utils-4.0.2
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git
omit dc186a6f Bump org.codehaus.plexus:plexus-utils from 4.0.0 to 4.0.2
add a6d9de11 Update Maven in GH workflow (#663)
add e0cb1e5f [MRESOLVER-680] Sigstore extension added (#662)
add ba361da1 [MRESOLVER-659] NPE in trusted checksum post processor if
artifact resolution failed (#665)
add 1c4cc088 Bump org.codehaus.plexus:plexus-utils from 4.0.0 to 4.0.2
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 (dc186a6f)
\
N -- N -- N
refs/heads/dependabot/maven/maven-resolver-1.9.x/org.codehaus.plexus-plexus-utils-4.0.2
(1c4cc088)
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 | 2 +-
.../aether/internal/impl/Maven2RepositoryLayoutFactory.java | 2 +-
.../TrustedChecksumsArtifactResolverPostProcessor.java | 2 +-
.../TrustedChecksumsArtifactResolverPostProcessorTest.java | 9 +++++++++
4 files changed, 12 insertions(+), 3 deletions(-)
