This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch 96fcdependabot/maven/org.apache.commons-commons-text-1.11.0 in repository https://gitbox.apache.org/repos/asf/maven-scm.git
discard 652525376 Bump org.apache.commons:commons-text from 1.10.0 to 1.11.0 add 90f9abc43 [SCM-1016] Update maven-parent to 41 (#195) add a018bfb5c Bump apache/maven-gh-actions-shared from 3 to 4 add 614500432 [SCM-1017] Bump commons-io:commons-io from 2.11.0 to 2.16.0 (#196) add 77ab56ea4 Bump org.apache.commons:commons-text from 1.10.0 to 1.11.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 (652525376) \ N -- N -- N refs/heads/96fcdependabot/maven/org.apache.commons-commons-text-1.11.0 (77ab56ea4) 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 +- maven-scm-client/pom.xml | 5 ---- .../maven-scm-provider-local/pom.xml | 4 +++ .../maven-scm-provider-git-commons/pom.xml | 4 +++ .../maven-scm-provider-svn-commons/pom.xml | 4 +++ maven-scm-test/pom.xml | 15 +++------- pom.xml | 34 ++-------------------- 7 files changed, 20 insertions(+), 48 deletions(-)