This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/maven.version-4.0.0-rc-2
in repository https://gitbox.apache.org/repos/asf/maven-mvnd.git
discard fe53ef5b Bump maven.version from 4.0.0-rc-1 to 4.0.0-rc-2
add ccb1cd1d Bump jline.version from 3.27.1 to 3.28.0 (#1226)
add 8b6abf17 Bump org.jboss.forge.roaster:roaster-jdt (#1227)
add 89f8cbfe Bump com.google.guava:guava from 33.3.1-jre to 33.4.0-jre
(#1231)
add 07090eb9 Bump maven.version from 4.0.0-rc-1 to 4.0.0-rc-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 (fe53ef5b)
\
N -- N -- N refs/heads/dependabot/maven/maven.version-4.0.0-rc-2
(07090eb9)
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 | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
