Version 27.1

This release fixes some bugs and performance regressions identified in v27.0.

[New in v27.1] Fixed an important performance regression in evaluation of range filter queries.
[New in v27.1] When infix search does not find highlight, use normal search.
[New in v27.1] Don't return error if limit_hits threshold is breached. Instead, just return empty results.
[New in v27.1] Add guard for non-indexed default sorting field.
[New in v27.1] Fix OpenAI error handling during conversation model init.
[New in v27.1] Fixed usage of distance_threshold parameter for inner product vector distance.
[New in v27.1] Fixed and improved validation for analytics rules and events.
[New in v27.1] Fixed an edge case with scoped API key usage with joins.
[New in v27.1] Fixed prefix highlighting bugs that occurred due to use of stemming.
[New in v27.1] Initialize analytics db store only if analytics dir is given. We will create a directory if it does not exist.
[New in v27.1] Fixed exporting regression that prevented embedding fields, joined fields and non-schema fields from being exported.
[New in v27.1] Fixed geo_distance_meters returning values in km / mi.

Upgrading

Before upgrading your existing Typesense cluster to v27.x, please review the behavior changes above to prepare your application for the upgrade.

We'd recommend testing on your development / staging environments before upgrading.

If you're on Typesense Cloud:

Go to https://cloud.typesense.org/clusters.
Click on your cluster
Click on "Cluster Configuration" on the left-side pane, and then click on "Modify"
Select a new Typesense Server version in the dropdown
Schedule a time for the upgrade.

If you're self-hosting Typesense, here are instructions on how to upgrade: https://typesense.org/docs/27.1/api/#self-hosted

Once you upgrade to v27 of Typesense Server, you can only downgrade back to v26 or v0.25.x.

View the complete API documentation for this release here: https://typesense.org/docs/27.1/api/