Cloudflare: op can now return "notContains"

What changed

Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.

Affects result.branches[][].op on POST /accounts/{account_id}/cloudforce-one/v2/priority-intelligence/filters/generate.

New value: notContains.

can now return "notContains"

Who is affected

Code that reads POST /accounts/{account_id}/cloudforce-one/v2/priority-intelligence/filters/generate (result.branches[][].op).

Before and after

Where	Before	After
POST /accounts/{account_id}/cloudforce-one/v2/priority-intelligence/filters/generate · result.branches[][].op	"contains", "endsWith", "equals", "find", "gt", "gte", "like", "lt", "lte", "not", "startsWith"	"contains", "endsWith", "equals", "find", "gt", "gte", "like", "lt", "lte", "not", "notContains", "startsWith"

Code that breaks

switch (response.result.branches[0][0].op) {
  // existing branches …
  // no branch for "notContains"
  default:
    throw new Error("unexpected op");
}

Based on Cloudflare’s published API specification. How severity is decided.