Bump Foundatio.Parsers.LuceneQueries from 7.18.3 to 8.0.0

[dependabot]

Updated Foundatio.Parsers.LuceneQueries from 7.18.3 to 8.0.0.

Release notes

Sourced from Foundatio.Parsers.LuceneQueries's releases.

8.0.0

v8.0.0

This is the first release Foundatio.Parsers 8.0, a major release centered on migrating Foundatio.Parsers.ElasticQueries from NEST to Elastic’s official Elastic.Clients.Elasticsearch stack, while keeping the Lucene parser and SQL/EF surfaces aligned with modern .NET.

Documentation: parsers.foundatio.dev, including the dedicated guide Upgrading to Elastic.Clients.Elasticsearch.

Compatibility note: This release references Elastic.Clients.Elasticsearch 8.19.x and is exercised against Elasticsearch 9.x in our Docker-based integration setup (see repo docker-compose.yml).

---

Themes

• Official Elasticsearch .NET client: NEST-era types (QueryContainer, AggregationContainer, IElasticClient, etc.) are replaced by first-class Elastic.Clients.Elasticsearch types (Query, AggregationMap, ElasticsearchClient, …). See #​84 and commit d91818b.
• Semantic versioning: 8.0 reflects breaking public API and dependency surface in the Elastic package, not Elasticsearch server version alone.
• Hardening and consistency in the Elastic stack: the #​84 work stream includes fixes for date/geo handling consistency (e.g. UTC-oriented field mapping timestamps, invariant-culture geo parsing), safer error messaging around Elasticsearch responses, and documentation for bool / OR / nested negation behavior differences vs NEST.
• System.Text.Json for Elasticsearch wire format: v8 aligns with Elastic.Clients.Elasticsearch, which uses System.Text.Json for request and response serialization, instead of the NEST / Elasticsearch.Net stack that typically pulled Json.NET (Newtonsoft.Json) transitively.

---

Breaking changes

• NEST removed; Elastic.Clients.Elasticsearch is required for all Elasticsearch query, aggregation, sort, and mapping integration. Remove direct NEST package references from consuming apps; add or rely on Elastic.Clients.Elasticsearch via Foundatio.Parsers.ElasticQueries. #​84
• Json.NET (Newtonsoft.Json) vs System.Text.Json: Dropping NEST and Elasticsearch.Net removes the older Elasticsearch .NET client stack that usually brought Newtonsoft.Json in as a transitive dependency and matched many samples and extensions to Json.NET. Elastic.Clients.Elasticsearch uses System.Text.Json end to end for client serialization. Foundatio.Parsers already used System.Text.Json for JSON normalization helpers in ElasticExtensions.cs; with v8 you should not expect Foundatio.Parsers.ElasticQueries to restore Newtonsoft for you. Audit any code that customized serialization, depended on Newtonsoft-only APIs from the legacy client, or assumed Json.NET defaults from those packages. Add an explicit Newtonsoft.Json reference only if other parts of your app still require it. #​84
• ElasticQueryParser build APIs return new types
  • BuildQueryAsync → Query (was QueryContainer).
  • BuildAggregationsAsync → AggregationMap (was AggregationContainer); use .ToDictionary() / .Aggregations() as in the upgrade guide.
  • BuildSortAsync → ICollection<SortOptions> (was IEnumerable<IFieldSort>).
• UseMappings and fluent mapping: builder shape moves from return-based Func to mutation-based Action, and ElasticsearchClient replaces IElasticClient. See the mapping tables in the upgrade guide.
• Custom visitors: SetQuery / GetQueryAsync use Query; aggregation helpers use AggregationMap; sorts use SortOptions. Type substitution table: upgrade guide: Custom Visitor Migration.
• IElasticQueryVisitorContext: implementations must supply GeoLocationResolver if they do not inherit from the default context type. Documented in the upgrade guide.
• Response checks: prefer IsValidResponse over NEST’s IsValid when validating client responses (see upgrade guide).
• Elasticsearch JSON / behavior (documented, some observable in generated queries)
  • Explicit minimum_should_match on OR / bool should clauses where the old NEST | operator implied it. The parser sets this explicitly for parity. #​84, upgrade guide.
  • Nested negation semantics corrected (negate the NestedQuery, not only the inner clause). upgrade guide.
  • Flatter bool.filter for non-scoring queries (equivalent but different JSON shape). upgrade guide.
  • Integer → long mapping note for @​field_type metadata with the new client’s conventions. upgrade guide.

---

Added

• AggregationMap: bridges parser aggregation building to the new client’s discriminated-union Aggregation model (see #​84 and AggregationMap.cs).
• First-class documentation for the migration path: Migrating to Elastic.Clients.Elasticsearch (source: docs/guide/upgrading-to-elastic-clients-elasticsearch.md), linked from the VitePress nav.

---

Changed

• Target frameworks: net8.0 and net10.0 (see build/common.props).
• Docs site dependencies: Bump uuid from 11.1.0 to 14.0.0 in /docs (#​229) (ca2ca96).
• Docs npm policy: 148cb8e lowers min-release-age from 7 to 3 days; 0d005b7 updates .npmrc for the documentation workspace.
  ... (truncated)

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)