Summary

This PR updates the documentation generation system for ESQL functions to correctly generate applies_to metadata in DocsV3, namely to support multiple versions and lifecycles.

This metadata is needed to signal version differentiation in the new docs, because we don't publish version-branched docs in 9.x (we don't duplicate every page for every minor).

For example, if something is preview in 9.0 and GA in 9.1 we need all this information on single, live 9.x page, that's what applies_to enables. Importantly, this also enables us to correctly signal serverless feature availability in the new docs.

We need different levels of applies_to discrimination for this:

• page annotations
• section annotations
• inline annotations.

Key changes

1. Documentation generation code

• x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/expression/function/Example.java - Added applies_to() field for version-specific examples
• x-pack/plugin/esql/src/test/java/org/elasticsearch/xpack/esql/expression/function/DocsV3Support.java - Updated to generate standardized applies_to blocks instead of manual callouts

2. Function status corrections

• All full-text search functions: now correctly marked as preview with proper applies_to syntax
• Spatial functions (ST_*): Added missing preview = true flags, and now use proper applies_to syntax
• A few other functions weren't correctly identifying inline version changes such as ToUpper supporting MVs in 9.1 only

3. Generated documentation updates

As a result all of the function code adjusted results in updated markdown and Kibana JSON file updates

Result

The documentation system now correctly generates version-aware metadata, enabling proper lifecycle tracking across versions. All full-text search functions are consistently marked as technical preview with the correct applies_to syntax, to enable us flipping them to GA for 9.1.

👀 URL preview