)]}'
{"releasenotes/notes/fix-reserve-volume-policy-31790a8d865ee0a1.yaml":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"965bd323c671209c6156cbde3847a96b79ea1b96","unresolved":false,"context_lines":[{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The reserve volume API was incorrectly enforcing \"volume:retype\" policy"},{"line_number":5,"context_line":"    action. It has been corrected to \"volume_extension:volume_actions:reserve\"."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"9f91af0f_8b25f5ad","line":5,"updated":"2018-01-03 16:53:53.000000000","message":"This was just added as part of the policy in code work. I don\u0027t think it needs a release note. Calling out fixes in release note is generally just for cases where we\u0027ve fixed major issues that users would have been working around in past releases.","commit_id":"678b9de0f43fa666946a064edc32f38514dfd593"}]}