chore: prepare release 2024-10-16

[shortcuts]

Summary

This PR has been created using the apic release script. Once merged, the clients will try to release their new version if their version has changed. https://algolia.atlassian.net/browse/DI-3078

Version Changes

• csharp: 7.6.1 -> patch (e.g. 7.6.2)
• dart: 1.26.1 -> patch (e.g. 1.26.2)
• go: 4.5.1 -> patch (e.g. 4.5.2)
• java: 4.5.1 -> patch (e.g. 4.5.2)
• javascript: 5.8.1 -> minor (e.g. 5.9.0)
• kotlin: 3.6.1 -> patch (e.g. 3.6.2)
• php: 4.6.1 -> patch (e.g. 4.6.2)
• python: 4.6.1 -> patch (e.g. 4.6.2)
• ruby: 3.5.1 -> patch (e.g. 3.5.2)
• scala: 2.5.1 -> patch (e.g. 2.5.2)
• swift: 9.7.1 -> patch (e.g. 9.7.2)

Skipped Commits

It doesn't mean these commits are being excluded from the release. It means they're not taken into account when the release process figured out the next version number, and updated the changelog.

Commits without language scope:

• fix(specs): recommend _score is optional

[algolia-bot]

✔️ Code generated!

Name	Link
🪓 Triggered by	376b194bcdf3b2ba455e2fdb80cd905f051a4dc4
🍃 Generated commit	6ed0d2679131e544ef5b87c1e1ee01bc4ea0e853
🌲 Generated branch	generated/chore/prepare-release-2024-10-16

📊 Benchmark results

Benchmarks performed on the method using a mock server, the results might not reflect the real-world performance.

Language	Req/s
go	1675
javascript	1579
php	1441
csharp	1373
java	1119
python	1034
ruby	887
swift	755

[shortcuts]

can't reproduce the error locally, upgrading vitest just in case

[shortcuts]

ok it works on a non release pr