summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorStephen Finucane <stephen@that.guru>2020-04-17 23:07:27 +0100
committerStephen Finucane <stephen@that.guru>2020-04-18 00:07:15 +0100
commit4fd7a739bbed62230d4166509929a35f63f6892e (patch)
treef07700b0a94a0e1211795304a83fb89bb109f92a /releasenotes
parentd08b6c72964898c9997a62e4ab6a721f166a56ca (diff)
downloadpatchwork-4fd7a739bbed62230d4166509929a35f63f6892e.tar
patchwork-4fd7a739bbed62230d4166509929a35f63f6892e.tar.gz
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
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/issue-357-1bef23dbfda2722d.yaml6
1 files changed, 6 insertions, 0 deletions
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>`__)