This is release 1.10 of the Search API, containing numerous new features and bug fixes.
Note: After upgrading, you might encounter the following log message:
SearchApiException: Required field search_api_access_node not indexed on index Default node index. Could not perform access checks. in _search_api_query_add_node_access()
If you have the "Node access" data alteration disabled, please disregard that message. This faulty message is a known problem, fixed with #2118589-22: Node access check missing from comment indexes, and a new 1.11 release containing that bugfix will be released shortly.
The main focus for this release was a revamp of the admin user interface undertaken with the help of Bojhan Somers. Hopefully, the UI improvements will make the Search API easier to use for new users, and also make common tasks reachable faster for existing ones. While a lot of areas were improved, most functionality should still be easy to find if you are used to the old UI, though.
If you have any questions, please create a support request issue (after making sure the question hasn't been answered already). If you have any more suggestions for UI improvements, please create a feature request issue using the Usability tag.
One particular UI improvement I want to mention was added in [##2130819]: on the index's "View" tab (which got merged with "Status") we now also check how many items are actually indexed on the server and can be found in a search – compared with the ones we think should be indexed, according to our tracking tables. This can help you spot any discrepancies that might have been caused by bugs in older versions of the module. (Particularly, we also fixed some related issues in #1551302: Fix server tasks system in this release.) If there are more or less items indexed on the server than their should be, a red warning will be displayed on the index's "View" tab. (When using Solr, however, a warning caused by too few indexed items on the server can also be due to Solr's commit behavior – wait a couple of minutes and see whether the warning is still there before taking any action). Also, if there are invalid items indexed on the server not associated with any index anymore, there is now also a button on the server's "View" tab to clear the complete indexed data of that server.
The release also contains fixes for the regressions accidentally introduced with #2110315: Specialized filter for users and terms in the 1.9 release. Please report there any issues you are still experiencing with taxonomy term filters.