update docs 0.8 - describe fix for aliased records

docs/changelog/changes_08.rst

@@ -6,7 +6,7 @@ Changes in 0.8
 
 - Introduce ``Schema`` . This is a new high-level api with aim to provide single entrypoint for validation/execution
   and query/mutations. Previously we had to manage two serapate graphs - one for Query other for Mutation or use `endpoint`
-  api but ``endpoint`` api is more like an integration-like api for http handlers.
+  api but ``endpoint`` api is more like an integration-like api for http handlers. More on that in :ref:`Schema docs <schema-doc>`.
 - ``Schema`` returns ``ExecutionResult`` dataclass with ``data``, ``errors`` and ``result`` fields. ``data`` already denormalized but access to `Proxy` object at ``result`` field is retained.
 - ``Endpoint`` now is much simpler under the hood and it basically delegates execution to schema, only providing support for batching.
 - Drop custom ``validate`` function for federation since we now have better support for ``_entities`` and ``_service`` fields and their corresponding types.
@@ -25,6 +25,21 @@ Changes in 0.8
 - Drop ``GraphQLError.errors`` field. Earlier we used to store multiple errors in single ``GraphQLError`` but now its one message - one ``GraphQLError``.
 - Add ``GraphQLError.message`` field
 - Dropped support for ``Python 3.7``, which ended support on 2023-06-27
+- Fix: now it is possible to alias record field:
+
+  .. code-block:: python
+
+    Graph([Root([Field("user", TypeRef["User"]))], data_types={"User": Record[{"id": Integer, "name": String}]})
+
+  .. code-block:: graphql
+
+    query {
+      user {
+        id
+        my_name: name
+      }
+    }
+
 
 Backward-incompatible changes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~