This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/scmVersion-2.1.0 in repository https://gitbox.apache.org/repos/asf/maven-release.git
discard 72083a54 Bump scmVersion from 2.0.1 to 2.1.0 add 869ad977 [MRELEASE-1146] maven-release-plugin tests do not properly check for existence of svn command add 2142c9e0 [MRELEASE-1144] Upgrade to Parent 42 add 8cf319e1 Bump scmVersion 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 (72083a54) \ N -- N -- N refs/heads/dependabot/maven/scmVersion-2.1.0 (8cf319e1) 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: .../src/it/projects/prepare/MRELEASE-1053/selector.groovy | 12 ++++++++++-- .../src/it/projects/prepare/MRELEASE-128/selector.groovy | 12 ++++++++++-- .../prepare/flat-multi-module/parent-project/selector.groovy | 12 ++++++++++-- .../it/projects/prepare/regular-multi-module/selector.groovy | 12 ++++++++++-- pom.xml | 4 ++-- 5 files changed, 42 insertions(+), 10 deletions(-) copy Jenkinsfile => maven-release-plugin/src/it/projects/prepare/MRELEASE-1053/selector.groovy (84%) copy Jenkinsfile => maven-release-plugin/src/it/projects/prepare/MRELEASE-128/selector.groovy (84%) copy Jenkinsfile => maven-release-plugin/src/it/projects/prepare/flat-multi-module/parent-project/selector.groovy (84%) copy Jenkinsfile => maven-release-plugin/src/it/projects/prepare/regular-multi-module/selector.groovy (84%)