This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch dependabot/maven/maven.version-4.0.0-rc-5
in repository https://gitbox.apache.org/repos/asf/maven-mvnd.git
discard 1dfbf10b Sync with rc5
discard b5f30c2a Adjust to API change in rc5
discard 737c099f Bump maven.version from 4.0.0-rc-4 to 4.0.0-rc-5
add ef4be6b9 Bump maven.resolver.version from 2.0.11 to 2.0.13
add f680a647 Bump org.graalvm.buildtools:native-maven-plugin from 0.11.2
to 0.11.3
add c5b87b77 Bump maven.version from 4.0.0-rc-4 to 4.0.0-rc-5
add ac7f5175 Adjust to rc5
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 (1dfbf10b)
\
N -- N -- N refs/heads/dependabot/maven/maven.version-4.0.0-rc-5
(ac7f5175)
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:
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
