curl --proto '=https' --tlsv1.2 -LsSf https://github.com/tursodatabase/turso/releases/download/v0.8.3/turso_cli-installer.sh | sh

powershell -ExecutionPolicy Bypass -c "irm https://github.com/tursodatabase/turso/releases/download/v0.8.3/turso_cli-installer.ps1 | iex"

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo tursodatabase/turso

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>

• #19813 common.socket Keep percent escapes in unix socket paths
• #19818 config Run processors once when there are no aggregators
• #19790 inputs.docker Pin API version for pre-1.40 daemons
• #19810 inputs.docker_log Pin API version for pre-1.40 daemons
• #19791 inputs.kinesis_consumer Emit the final records of a closed shard
• #19855 inputs.snmp Drop the connection to an agent after a failed gather

• #19759 deps Bump cloud.google.com/go/auth from 0.23.2 to 0.23.3
• #19798 deps Bump cloud.google.com/go/auth from 0.23.3 to 0.24.0
• #19772 deps Bump cloud.google.com/go/bigquery from 1.83.0 to 1.84.0
• #19804 deps Bump cloud.google.com/go/bigquery from 1.84.0 to 1.85.0
• #19796 deps Bump cloud.google.com/go/monitoring from 1.30.0 to 1.31.0
• #19758 deps Bump cloud.google.com/go/storage from 1.67.1 to 1.68.0
• #19827 deps Bump cloud.google.com/go/storage from 1.68.0 to 1.69.0
• #19832 deps Bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.23.1 to 1.23.2
• #19799 deps Bump github.com/IBM/sarama from 1.60.2 to 1.61.0
• #19826 deps Bump github.com/IBM/sarama from 1.61.0 to 1.61.1
• #19835 deps Bump github.com/SAP/go-hdb from 1.18.10 to 1.19.0
• #19767 deps Bump github.com/SAP/go-hdb from 1.18.4 to 1.18.9
• #19797 deps Bump github.com/SAP/go-hdb from 1.18.9 to 1.18.10
• #19844 deps Bump github.com/apache/thrift from 0.24.0 to 0.25.0
• #19765 deps Bump github.com/aws/smithy-go from 1.28.1 to 1.28.2
• #19760 deps Bump github.com/dustin/go-humanize from 1.0.1 to 1.1.0
• #19769 deps Bump github.com/gopacket/gopacket from 1.7.1 to 1.7.2
• #19836 deps Bump github.com/gopacket/gopacket from 1.7.2 to 1.7.4
• #19757 deps Bump github.com/gophercloud/gophercloud/v2 from 2.14.0 to 2.15.0
• #19802 deps Bump github.com/gosnmp/gosnmp from 1.44.0 to 1.45.0
• #19794 deps Bump github.com/hashicorp/go-uuid from 1.0.3 to 1.0.4
• #19831 deps Bump github.com/jaypipes/ghw from 0.25.0 to 0.26.0
• #19793 deps Bump github.com/klauspost/compress from 1.20.0 to 1.20.1
• #19839 deps Bump github.com/klauspost/pgzip from 1.2.6 to 1.2.7
• #19807 deps Bump github.com/lxc/incus/v7 from 7.4.0 to 7.5.1
• #19803 deps Bump github.com/microsoft/go-mssqldb from 1.11.0 to 1.11.2
• #19830 deps Bump github.com/moby/moby/api from 1.56.0 to 1.56.1
• #19825 deps Bump github.com/moby/moby/client from 0.6.0 to 0.6.1
• #19771 deps Bump github.com/nats-io/nats-server/v2 from 2.14.6 to 2.15.0
• #19766 deps Bump github.com/nats-io/nats.go from 1.53.1 to 1.54.0
• #19837 deps Bump github.com/netsampler/goflow2/v2 from 2.2.6 to 2.2.7
• #19761 deps Bump github.com/pion/dtls/v3 from 3.1.8 to 3.1.9
• #19795 deps Bump github.com/prometheus/prometheus from 0.314.0 to 0.315.0
• #19770 deps Bump github.com/rabbitmq/amqp091-go from 1.14.0 to 1.15.0
• #19843 deps Bump github.com/shirou/gopsutil/v4 from 4.26.8 to 4.26.9
• #19841 deps Bump github.com/snowflakedb/gosnowflake/v2 from 2.2.0 to 2.3.0
• #19800 deps Bump github.com/tdrn-org/go-hue from 1.2.1 to 1.2.2
• #19833 deps Bump github.com/tdrn-org/go-hue from 1.2.2 to 1.2.3
• #19829 deps Bump github.com/tdrn-org/go-nsdp from 0.5.1 to 0.5.3
• #19834 deps Bump github.com/tdrn-org/go-tr064 from 0.3.0 to 0.4.0
• #19845 deps Bump github.com/tinylib/msgp from 1.6.4 to 1.6.5
• #19764 deps Bump go.opentelemetry.io/collector/pdata from 1.66.0 to 1.67.0
• #19847 deps Bump go.opentelemetry.io/collector/pdata from 1.67.0 to 1.68.0
• #19840 deps Bump go.opentelemetry.io/proto/otlp/collector/profiles/v1development from 0.4.0 to 0.4.1
• #19842 deps Bump go.opentelemetry.io/proto/otlp/profiles/v1development from 0.4.0 to 0.4.1
• #19768 deps Bump go.step.sm/crypto from 0.90.0 to 0.91.0
• #19846 deps Bump golang.org/x/tools from 0.50.0 to 0.51.0
• #19801 deps Bump google.golang.org/api from 0.297.0 to 0.299.0
• #19806 deps Bump k8s.io/apimachinery from 0.37.0 to 0.37.1
• #19805 deps Bump k8s.io/client-go from 0.37.0 to 0.37.1
• #19762 deps Bump modernc.org/sqlite from 1.58.0 to 1.59.0
• #19838 deps Bump modernc.org/sqlite from 1.59.0 to 1.60.1
• #19823 deps Bump super-linter/super-linter from 8.7.0 to 9.0.0
• #19792 deps Bump the aws-sdk-go-v2 group across 1 directory with 11 updates
• #19756 deps Bump the aws-sdk-go-v2 group across 1 directory with 7 updates
• #19824 deps Bump the aws-sdk-go-v2 group with 3 updates

Apply an inline-specified dynamic search rule to a search query.

Search query objects in the following endpoints now have an additional, optional inlineRule parameter.

When present and not null, then Meilisearch will check if query satisfies the conditions of the dynamic search rule specified in inlineRule, and if so will apply the actions of the rule as if it had been sent to the PATCH /dynamicSearchRule/{:uid} endpoint.

Additionally, if the Meili-Include-Metadata header is present in the request with the value true, then the metadata in the response will contain information about whether the conditions of the inline rule were satisfied and if not why.

Meilisearch Cloud will use this backend feature to implement a preview UI for dynamic search rules.

Using inlineRule requires Meilisearch Enterprise Edition and the dynamicSearchRules experimental feature.

By @dureuill in https://github.com/meilisearch/meilisearch/pull/6669

1. There is a new InlineRule object with the following field:
   1. uid, string, mandatory: unique ID of the rule. If there is already a rule with this id, then the inline rule will replace the existing rule for the duration of this search query.
   2. active, boolean, optional, defaults to true: whether the rule is active. The actions of an inactive inline rule never apply to the search, but its conditions are still checked
   3. conditions: RuleConditions object, identical to the conditions field in the body of PATCH /dynamic-search-rules/{:uid}
   4. actions: RuleActions object, identical to the actions field in the body of PATCH /dynamic-search-rules/{:uid}
   5. precedence: integer, optional, identical to the precedence field in the body of PATCH /dynamic-search-rules/{:uid}
2. The POST /indexes/{:indexUid}/search body has an additional, optional (defaults to null) inlineRule field which is an InlineRule object.
3. In the POST /multi-search body, the objects inside the queries array have an additional, optional (defaults to null) inlineRule field which is an InlineRule object.

// POST /indexes/movies/search
{
  "q": "super hero",
  "inlineRule": {
    "uid": "user-likes-batman",
    "actions": {
      "scale": [
        {
          // filter recent Batman movies
          "filter": "hero = batman AND release_time = fresh",
          "weight": 1.2 // moderate relevancy boost
        }
      ]
    }
  }
}

// POST /multi-search -H 'Meili-Include-Metadata: true`

{
  "queries": [
    // base query without inline rule
    {
      "q": "fashion",
      "filter": "color = blue AND category = shirt"
    },
    // same query with inline rule
    {
      "q": "fashion",
      "filter": "color = blue AND category = shirt",
      "inlineRule": {
        "uid": "special-sales",
        "conditions": {
          "query": {
            "words": "pants",
          },
            "filter": {
              "values": {
                "color":  "yellow",
                "stock_intent": "destock"
            }
          }
        }
      }
    }
  ]
}

{
  // [ ... ] some other fields
  "results": [
    // results without the rule
    {
      "hits": [ ... ] // documents returned without the rule
    },
    // results with the rule
    {
      // [...] some other fields
      "hits": [...], // documents returned with the rule. Here the same, because the conditions of the rules are not satisfied
      "metadata": {
        // [...] some other fields
        "inlineRuleConditionOutcomes":  {
          "satisfiesActiveCondition": true,
          "satisfiesQueryWordsCondition": {
            "missingWord": "pants"
          },
        "satifiesFilterCondition": {
          "missingConstraintOnField": {
            "field":  "stock_intent"
          },
          "unmetConstraintOnField": 
            "field": "color"
          }
        }
      }
    }
  ]
}

When setting showPerformanceDetails to true in a search request, the response's performanceDetails will now display an entry for the facet distribution computation.

curl -X POST 'http://localhost:7700/indexes/movies/search' \
  -H 'Content-Type: application/json' \
  -d '{
    "q": "batman",
    "facets": ["genres"],
    "showPerformanceDetails": true,
    "limit": 3
  }'

{
    "hits": [
		# ...
    ],
    "query": "batman",
    "processingTimeMs": 4,
    "limit": 3,
    "offset": 0,
    "estimatedTotalHits": 68,
    "facetDistribution": {
        "genres": {
			#...
        }
    },
    "facetStats": {},
    "requestUid": "01a12f80-0e1b-7632-b4f3-c8d4914048c9",
    "performanceDetails": {
        "wait in queue": "68.58µs",
        "preprocess filters > prepare": "100.25µs",
        "preprocess filters": "100.42µs",
        "process > prepare": "115.54µs",
        "process > send to remote": "102.71µs",
        "process > execute local > load field ids map": "30.88µs",
        "process > execute local > query[0] > tokenize query": "265.38µs",
        "process > execute local > query[0] > evaluate query": "890.96µs",
        "process > execute local > query[0] > keyword ranking": "425.04µs",
        "process > execute local > query[0]": "2.95ms",
        "process > execute local > pin hits": "9.92µs",
        "process > execute local > format": "94.62µs",
        "process > execute local > facet distribution > compute facet distribution": "315.75µs",
        "process > execute local > facet distribution > compute facet stats": "27.71µs",
        "process > execute local > facet distribution": "432.62µs",
        "process > execute local": "3.81ms",
        "process > wait for remote": "50.96µs",
        "process > merge": "905.62µs",
        "process": "5.07ms"
    }
}

        "process > execute local > facet distribution > compute facet distribution": "315.75µs",
        "process > execute local > facet distribution > compute facet stats": "27.71µs",
        "process > execute local > facet distribution": "432.62µs",

By @ManyTheFish in https://github.com/meilisearch/meilisearch/pull/6644

Documents containing raw unicode codepoints (e.g. \u03b1) would cause a panic at search time when formatting results for highlighting when using some segmenters.

A failure at the segmenter's level no longer causes a panic.

By @dureuill in https://github.com/meilisearch/meilisearch/pull/6673

[!IMPORTANT]
This fix modifies the relevancy of the engine in some circumstances. This is allowed as per our back-compatiblity policy.

To avoid a performance sink when using the rankingScoreThreshold parameter in a search, Meilisearch now guarantees that the search will stop after evaluating the first document whose score is below the threshold. Previously Meilisearch would try to evaluate more documents, which could lead to evaluating all documents in the database, causing a very long search time.

By @ManyTheFish in https://github.com/meilisearch/meilisearch/pull/6661

[!WARNING]
This fix introduces a breaking change in the Meilisearch API. Because the previous behavior would corrupt the embeddings in the database, this is allowed by our back-compatibility policy.

Since the exact value of embeddings is not retained when the embedder is configured for binary quantize embeddings, disabling the binary quantization on an index is not allowed.

Unfortunately, an oversight in the API allowed to accidentally disable binary quantization by passing binaryQuantization: null in a setting update. This now results in an error.

By @dureuill in https://github.com/meilisearch/meilisearch/pull/6656

• Maintainability: replace some unreachable!() code paths with static typing by @dureuill in https://github.com/meilisearch/meilisearch/pull/6670
• Add GHA to enforce benchmarks label on each PR by @curquiza in https://github.com/meilisearch/meilisearch/pull/6663
• Add link to MCP guide in generated API reference by @Strift in https://github.com/meilisearch/meilisearch/pull/6650
• Add link to agentic search demo & fix links by @Strift in https://github.com/meilisearch/meilisearch/pull/6655
• Small changes to CONTRIBUTING.md by @dureuill in https://github.com/meilisearch/meilisearch/pull/6668
• Bump actions/setup-java from 5.7.0 to 6.0.1 by @dependabot[bot] in https://github.com/meilisearch/meilisearch/pull/6662
• Fix OpenAPI docs by @curquiza in https://github.com/meilisearch/meilisearch/pull/6667
• CI: Fix flaky tests by @dureuill in https://github.com/meilisearch/meilisearch/pull/6674

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.54.3...v1.55.0

Download Kong 3.9.4 and run it now:

https://konghq.com/install/ Docker Image

Links:

3.9.4 Changelog

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/tursodatabase/turso/releases/download/v0.8.3-pre.2/turso_cli-installer.sh | sh

powershell -ExecutionPolicy Bypass -c "irm https://github.com/tursodatabase/turso/releases/download/v0.8.3-pre.2/turso_cli-installer.ps1 | iex"

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo tursodatabase/turso

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>