This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.scm-maven-scm-provider-svnexe-2.1.0
in repository https://gitbox.apache.org/repos/asf/ws-xmlschema.git
discard daf607e1 Bump org.apache.maven.scm:maven-scm-provider-svnexe from
2.0.1 to 2.1.0
add 2dcd390a Bump com.google.guava:guava-testlib from 33.0.0-jre to
33.2.0-jre
add 9ebca8b0 Adding pull request builder
add dc5c4dec Removing source-plugin
add e738abf9 Revert "Adding pull request builder"
add be40a18a Bump org.apache:apache from 23 to 33 (#57)
add 8ff11e5c Bump org.apache.maven.scm:maven-scm-provider-svnexe from
2.0.1 to 2.1.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 (daf607e1)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.scm-maven-scm-provider-svnexe-2.1.0
(8ff11e5c)
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 | 28 +++-------------------------
1 file changed, 3 insertions(+), 25 deletions(-)
