Platform 2026.09.09
Breaking Change
- Stricter YAML parsing: The YAML parser now rejects unsafe input instead of silently rewriting it, so three patterns that used to deploy will now fail. A file carrying one of them has been deploying a value other than the one it reads, so this is worth checking before you upgrade.
:draft— a leading colon. Remove the colon.!ruby/object:Foo— delete the tag declaration.*missing— an orphaned alias. Make sure a matching anchor exists.
Standard YAML features are unaffected: anchors, aliases, merges and dates all continue to work.
Bug Fix
- JSON error responses for unparsable bodies: A request sent with
Content-Type: application/jsonwhose body is malformed now receives a structured JSON error,{"status":400,"error":"There was a problem in the JSON you submitted: ..."}, instead of plain text. Other content types still receive a text response, now with an explicitContent-Type: text/plainheader.