This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/quarkus-mcp-server-version-1.10.3
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 14921cbb96ec chore(deps): Bump quarkus-mcp-server-version from 1.10.2
to 1.10.3
add 0ca30b330ef2 Revert "CAMEL-23141: Hoist storedFields() out of the
search loop"
add a2187651ec7b Revert "CAMEL-23141 replace deprecated search method"
add bcb72c2c8383 Revert "CAMEL-23141 update Lucene to 10.x"
add d34f56c8ee42 chore(deps): Bump quarkus-mcp-server-version from 1.10.2
to 1.10.3
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 (14921cbb96ec)
\
N -- N -- N
refs/heads/dependabot/maven/quarkus-mcp-server-version-1.10.3 (d34f56c8ee42)
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:
.../org/apache/camel/component/lucene/LuceneSearcher.java | 14 +++++---------
parent/pom.xml | 2 +-
2 files changed, 6 insertions(+), 10 deletions(-)
