chore(2meet-data-optimizer): 1.4.1 release notes and version

- CHANGELOG / readme: PR-130..133 (2.4 acceptance review fixes) - Version 1.4.0 -> 1.4.1 (header, TMDO_VERSION, Stable tag) - PR: PR-134
2026-09-28 00:46:56 +08:00
parent 3e96357459
commit 81324903a6
3 changed files with 40 additions and 3 deletions
@@ -4,7 +4,7 @@ Tags: performance, database, postmeta, optimization, hivepress
 Requires at least: 6.0
 Tested up to: 6.9
 Requires PHP: 8.1
-Stable tag: 1.4.0
+Stable tag: 1.4.1
 License: GPLv2 or later
 License URI: https://www.gnu.org/licenses/gpl-2.0.html

@@ -107,6 +107,12 @@ The Classifier tab analyzes your existing `wp_postmeta` data (access frequency,

 == Changelog ==

+= 1.4.1 =
+* A query ordered by its meta_key among several orderings (or by the key's name) keeps meta_key native; meta_compare_key other than '=' is not routed; a sort group stays when orderby may use it as the primary clause
+* Only standalone posts.ID terms in ORDER BY become flat post_id tie-breaks (FIELD()/IN expressions from other plugins are left alone); PCRE failures keep the original SQL
+* Router query vars preset by callers are dropped
+* New posts' flat rows get their status/date copies; post-status-sync invalidates cached routed counts
+
 = 1.4.0 =
 * Flat-first sorts read the ID tie-break from the flat post_id, so a declared (column, post_id) index returns rows in order; ties now follow the sort direction
 * Meta clauses without a value route as EXISTS; HivePress's featured-listing lookup on every search page uses the flat table