This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/lucene.version-10.2.1
in repository https://gitbox.apache.org/repos/asf/maven-indexer.git
discard 3d60da2 Bump lucene.version from 9.11.1 to 10.2.1
add 2b6b88a [MINDEXER-243] Bump
org.apache.maven.archetype:archetype-catalog from 3.2.1 to 3.4.0 (#421)
add e9ffb31 [MINDEXER-244] Bump com.google.code.gson:gson from 2.11.0 to
2.13.1 (#420)
add 96eafec [MINDEXER-245] Bump org.jsoup:jsoup from 1.18.1 to 1.20.1
(#417)
add 95ebc0a [MINDEXER-246] Bump org.eclipse.sisu:org.eclipse.sisu.inject
from 0.9.0.M3 to 0.9.0.M4 (#418)
add 5e6c58f [MINDEXER-247] Bump com.google.guava:guava from 33.3.0-jre to
33.4.8-jre (#419)
add 7bda869 [MINDEXER-248] Bump lucene.version from 9.11.1 to 9.12.1
(#422)
add df0bf37 Bump lucene.version from 9.11.1 to 10.2.1
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 (3d60da2)
\
N -- N -- N refs/heads/dependabot/maven/lucene.version-10.2.1
(df0bf37)
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 +++---
search-backend-remoterepository/pom.xml | 2 +-
search-backend-smo/pom.xml | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
