Merge pull request #402 from timescale/fix/2.27.2-order

Put v2.27.2 in the right position based on date

Author: atovpeko

src/content/docs/get-started/news/new.mdx

@@ -242,44 +242,6 @@ It is now the default in Tiger Cloud, so check it out.
 <Image src={imgServiceCreationFlowTigerCloud} alt="Step 1 of the updated Tiger Cloud service creation flow, showing compute and region selection with a live cost estimate" />
 </ChangelogEntry>
 
-## TimescaleDB v2.27.2 now on Tiger Cloud
-
-<ChangelogEntry
-  title="TimescaleDB v2.27.2 now on Tiger Cloud"
-  date="2026-06-22"
-  tags={["bug-fix", "security-fix"]}
->
-<h2 slot="heading" class="changelog-entry__title">TimescaleDB v2.27.2 now on Tiger Cloud</h2>
-
-TimescaleDB v2.27.2 is a stability and security patch that supersedes 2.27.1 on Tiger Cloud. Together, 2.27.1 and 2.27.2 close three access-control gaps in the jobs and policy subsystems, fix a correctness bug in grouped aggregation on the columnstore, refine the columnstore query planner, and ship upgrade-compatibility scripts for composite bloom filter metadata. TimescaleDB 2.27.1 was released on May 19, 2026 and 2.27.2 on June 2, 2026; both are delivered to Tiger Cloud as 2.27.2 starting June 22, 2026.
-
-### Highlighted fixes in TimescaleDB v2.27.2
-
-**Tightened access controls**
-
-Three independent fixes in the jobs and policy subsystems close cases where users could observe or act on objects they did not own.
-
-- **Hypertable ownership enforced before recompression:** Recompression operations now verify ownership before proceeding. Previously, users could trigger recompression on hypertables they did not own.
-
-- **`job_errors` view restricted to owners:** Failed-job visibility is now scoped — only owners see failure rows for their own jobs. Previously, non-owners could read failure information they should not have had access to.
-
-- **`policy_reorder_remove` ownership check added:** The policy-management operation now enforces ownership before allowing changes, closing a path that previously leaked policy-existence information to non-owners.
-
-**Correctness and planner refinements on the columnstore**
-
-- **Correct results for `GROUP BY` columns not in the `SELECT` list:** Queries grouping by a column not included in the `SELECT` list could return incorrect rows or crash when running through vectorized aggregation or `ColumnarIndexScan`. This is now fixed — no SQL change required.
-
-- **Safer `ColumnarIndexScan` planning:** The path now correctly bypasses query shapes it can't safely handle — including `GROUPING SETS` / `ROLLUP` / `CUBE`, grouping by expressions, and `WHERE` clauses containing subplans — avoiding inefficient or incorrect plan choices.
-
-**Operational fixes**
-
-- **Columnstore policy creation no longer blocked by stale refresh-policy check:** Adding a columnstore policy was failing in some workflows due to an unnecessary check on existing refresh policies. The check has been removed.
-
-- **Upgrade compatibility:** The upgrade path now cleans up orphaned `compression_settings` rows before migrating the catalog, and ships migration scripts for installations carrying composite bloom filter metadata (complementing the format change in 2.27.0).
-
-For complete details, refer to the [TimescaleDB 2.27.1 release notes](https://github.com/timescale/timescaledb/releases/tag/2.27.1) and the [TimescaleDB 2.27.2 release notes](https://github.com/timescale/timescaledb/releases/tag/2.27.2).
-</ChangelogEntry>
-
 ## Automated chunk tuning is now GA
 
 <ChangelogEntry 
@@ -318,6 +280,44 @@ See all available regions in [Supported regions](/learn/tiger-cloud/regions).
 
 </ChangelogEntry>
 
+## TimescaleDB v2.27.2 now on Tiger Cloud
+
+<ChangelogEntry
+  title="TimescaleDB v2.27.2 now on Tiger Cloud"
+  date="2026-06-22"
+  tags={["bug-fix", "security-fix"]}
+>
+<h2 slot="heading" class="changelog-entry__title">TimescaleDB v2.27.2 now on Tiger Cloud</h2>
+
+TimescaleDB v2.27.2 is a stability and security patch that supersedes 2.27.1 on Tiger Cloud. Together, 2.27.1 and 2.27.2 close three access-control gaps in the jobs and policy subsystems, fix a correctness bug in grouped aggregation on the columnstore, refine the columnstore query planner, and ship upgrade-compatibility scripts for composite bloom filter metadata. TimescaleDB 2.27.1 was released on May 19, 2026 and 2.27.2 on June 2, 2026; both are delivered to Tiger Cloud as 2.27.2 starting June 22, 2026.
+
+### Highlighted fixes in TimescaleDB v2.27.2
+
+**Tightened access controls**
+
+Three independent fixes in the jobs and policy subsystems close cases where users could observe or act on objects they did not own.
+
+- **Hypertable ownership enforced before recompression:** Recompression operations now verify ownership before proceeding. Previously, users could trigger recompression on hypertables they did not own.
+
+- **`job_errors` view restricted to owners:** Failed-job visibility is now scoped — only owners see failure rows for their own jobs. Previously, non-owners could read failure information they should not have had access to.
+
+- **`policy_reorder_remove` ownership check added:** The policy-management operation now enforces ownership before allowing changes, closing a path that previously leaked policy-existence information to non-owners.
+
+**Correctness and planner refinements on the columnstore**
+
+- **Correct results for `GROUP BY` columns not in the `SELECT` list:** Queries grouping by a column not included in the `SELECT` list could return incorrect rows or crash when running through vectorized aggregation or `ColumnarIndexScan`. This is now fixed — no SQL change required.
+
+- **Safer `ColumnarIndexScan` planning:** The path now correctly bypasses query shapes it can't safely handle — including `GROUPING SETS` / `ROLLUP` / `CUBE`, grouping by expressions, and `WHERE` clauses containing subplans — avoiding inefficient or incorrect plan choices.
+
+**Operational fixes**
+
+- **Columnstore policy creation no longer blocked by stale refresh-policy check:** Adding a columnstore policy was failing in some workflows due to an unnecessary check on existing refresh policies. The check has been removed.
+
+- **Upgrade compatibility:** The upgrade path now cleans up orphaned `compression_settings` rows before migrating the catalog, and ships migration scripts for installations carrying composite bloom filter metadata (complementing the format change in 2.27.0).
+
+For complete details, refer to the [TimescaleDB 2.27.1 release notes](https://github.com/timescale/timescaledb/releases/tag/2.27.1) and the [TimescaleDB 2.27.2 release notes](https://github.com/timescale/timescaledb/releases/tag/2.27.2).
+</ChangelogEntry>
+
 ## Updates to the Goals flow in Tiger Console
 
 <ChangelogEntry