docs: fix release version of json bytes dump support

It is to be released in 3.1.10, not already released in 3.1.9... See #568

diff --git a/docs/news.rst b/docs/news.rst
index ff670804ae38ff0d6cbca465b0fd6f200c7f0e9a..5a5bfc6c3f0b94a2f7177e0bb82ff8282b4dcdd9 100644 (file)
--- a/docs/news.rst
+++ b/docs/news.rst
@@ -13,6 +13,9 @@ Future releases
 Psycopg 3.1.10 (unreleased)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
+- Allow JSON dumpers to dump `bytes` directly instead of `str`,
+  for better compatibility with libraries like orjson and msgspec
+  (:ticket:`#569`)
 - Fix prepared statement cache validation when exiting pipeline mode (or
   `~Cursor.executemany()`) in case an error occurred within the pipeline
   (:ticket:`#585`).
@@ -45,14 +48,12 @@ Psycopg 3.1.9
 - Fix loading ROW values with different types in the same query using the
   binary protocol (:ticket:`#545`).
 - Fix dumping recursive composite types (:ticket:`#547`).
-- Allow JSON dumpers to dump `bytes` directly instead of `str`,
-  for better compatibility with libraries like orjson and msgspec (:ticket:`#569`)
 
 
 Psycopg 3.1.8
 ^^^^^^^^^^^^^
 
-- Don't pollute server logs when types looked for by `TypeInfo.fetch()` 
+- Don't pollute server logs when types looked for by `TypeInfo.fetch()`
   are not found (:ticket:`#473`).
 - Set `Cursor.rowcount` to the number of rows of each result set from
   `~Cursor.executemany()` when called with `!returning=True` (:ticket:`#479`).