From 4fd7a739bbed62230d4166509929a35f63f6892e Mon Sep 17 00:00:00 2001
From: Stephen Finucane <stephen@that.guru>
Date: Fri, 17 Apr 2020 23:07:27 +0100
Subject: REST: Allow update of bundle without patches

Presently, when updating a patch we assume that patches are provided.
This isn't necessary - you might just want to make it public - and isn't
enforced by the API itself. However, because we make this assumption, we
see a HTTP 500. Resolve the issue and add tests to prevent a regression.

Signed-off-by: Stephen Finucane <stephen@that.guru>
Resolves: #357
---
 releasenotes/notes/issue-357-1bef23dbfda2722d.yaml | 6 ++++++
 1 file changed, 6 insertions(+)
 create mode 100644 releasenotes/notes/issue-357-1bef23dbfda2722d.yaml

(limited to 'releasenotes')

diff --git a/releasenotes/notes/issue-357-1bef23dbfda2722d.yaml b/releasenotes/notes/issue-357-1bef23dbfda2722d.yaml
new file mode 100644
index 0000000..1f337c7
--- /dev/null
+++ b/releasenotes/notes/issue-357-1bef23dbfda2722d.yaml
@@ -0,0 +1,6 @@
+---
+fixes:
+  - |
+    An issue that preventing updating bundles via the REST API without
+    updating the included patches has been resolved.
+    (`#357 <https://github.com/getpatchwork/patchwork/issues/357>`__)
-- 
cgit v1.2.3