This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/lucene.version-10.3.2
in repository https://gitbox.apache.org/repos/asf/maven-indexer.git
discard fb10158 Bump lucene.version from 9.12.1 to 10.3.2
add 97a7c24 Bump commons-cli:commons-cli from 1.10.0 to 1.11.0 (#712)
add 0d3e467 Bump org.ow2.asm:asm from 9.9 to 9.9.1 (#715)
add 7d21e5c Bump resolver.version from 2.0.13 to 2.0.14 (#714)
add 8b2f643 Bump maven.version from 3.9.11 to 3.9.12 (#716)
add de95999 Bump lucene.version from 9.12.1 to 10.3.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 (fb10158)
\
N -- N -- N refs/heads/dependabot/maven/lucene.version-10.3.2
(de95999)
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:
indexer-cli/pom.xml | 2 +-
pom.xml | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
