[PATCH v4 7/7] release-notes: Add release note

[Adam Hassick]

Signed-off-by: Adam Hassick <ahassick at iol.unh.edu>
---
 ...-series-dependencies-6696458586e795c7.yaml | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 releasenotes/notes/add-series-dependencies-6696458586e795c7.yaml

diff --git a/releasenotes/notes/add-series-dependencies-6696458586e795c7.yaml b/releasenotes/notes/add-series-dependencies-6696458586e795c7.yaml
new file mode 100644
index 0000000..89ab91f
--- /dev/null
+++ b/releasenotes/notes/add-series-dependencies-6696458586e795c7.yaml
@@ -0,0 +1,22 @@
+---
+features:
+  - |
+    Series may now depend on each other. Patchwork clients may use this
+    information to download and apply the dependencies when applying a series.
+    This dependency relationship is shallow; the dependencies of a dependency
+    should not be applied. Multiple dependencies are allowed. The order they
+    are applied in is the order they appear in the content from top to bottom.
+  - |
+    Patchwork will now look for "Depends-on" entries when parsing mails.
+    This may be done by referring to a patch or cover letter message ID in the
+    commit message of a patch or the cover letter content:
+    ``Depends-on: <20240726221429.221611-1-user at example.com>``
+    Alternatively, the web URL of the patch or series may be given:
+    ``Depends-on: http://patchwork.example.com/project/test/list?series=1111``
+api:
+  - The API version has been updated to v1.4.
+  - Add the "dependencies" and "dependents" fields to the series detail view.
+  - |
+    Add the "parse_dependencies" field to projects. When this field is set to
+    ``True``, the "Depends-on" parsing feature will be enabled for any patches
+    and cover letters received for that project.
-- 
2.48.1