API and transaction assertions compare values by type

JSONPath assertions using equals or not equals now compare by JSON type. true, false and null match JSON booleans and null, and JSON text such as [] matches arrays and objects by structure. Before, $.degraded equals false passed even when the API returned true, and $.items not equals [] passed on an empty list.

There is also a new does not contain operator. For Body contains, not equals now means "does not contain", and a JSONPath assertion against a response that is not valid JSON (an HTML page, an empty or cut-off body) now fails whatever its operator.

Some monitors may change state after this update, because they now evaluate as written. Review monitors that use equals/not equals with true, false, null or [], that pair Body contains with not equals, or that run JSONPath assertions against responses that are not JSON.

Keyword, API, transaction and content-change monitors on pages in other languages or older character sets, which sometimes failed with "Check aborted unexpectedly.", now check normally. Characters that can't be read are shown as �.