ephraimbuddy commented on code in PR #58394:
URL: https://github.com/apache/airflow/pull/58394#discussion_r2536609538


##########
clients/python/CHANGELOG.md:
##########
@@ -17,6 +17,27 @@
  under the License.
  -->
 
+# v3.1.3
+
+## Major changes:
+
+- Add query limit protection to prevent excessive database queries in DAG runs 
list endpoints ([#57450](https://github.com/apache/airflow/pull/57450))
+- Change `extra` field type to `dict[str, JsonValue]` for Asset, AssetAlias, 
and AssetEvent models ([#57352](https://github.com/apache/airflow/pull/57352))

Review Comment:
   From the release [guide 
](https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PYTHON_CLIENT.md),
 we have to make this PR against main and cherrypick to the test branch, from 
where we merge to the stable branch as if doing a normal release. There's the 
below instruction in the guide and it is how we had been doing it:
   
   ```
   - Update CHANGELOG.md with the details.
   - Create PR where you add the changelog in main branch and cherry-pick it to 
the v2-test branch - same as in case of Airflow changelog.
   ```
   
   
   
   
   



##########
clients/python/CHANGELOG.md:
##########
@@ -17,6 +17,27 @@
  under the License.
  -->
 
+# v3.1.3
+
+## Major changes:
+
+- Add query limit protection to prevent excessive database queries in DAG runs 
list endpoints ([#57450](https://github.com/apache/airflow/pull/57450))
+- Change `extra` field type to `dict[str, JsonValue]` for Asset, AssetAlias, 
and AssetEvent models ([#57352](https://github.com/apache/airflow/pull/57352))

Review Comment:
   So, we are not releasing it from main but still the same process you 
described, only that we merge to the stable branch.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to