Version dates

• PrPr 2026-10-06 now also applies to PATCH /v1/monitors/{id}, so the version covers GET, POST, PATCH, and DELETE. On PATCH, the versioned request takes Monitor-UpdateRequest, a JSON merge patch (RFC 7396) over the writable fields of Monitor-Resource, and the response is 200 with the updated Monitor-Resource instead of 204 with no body. Omitted fields keep their value, objects merge member by member, arrays replace the whole list, and null resets a field to its default. A name already in use, a monitor changed while the patch was applied, and a patch that sets inputQuery on a monitor reading a query parameter return 409. It is alpha and returns 403 until the account is enabled; callers without the header keep the stable default request and behavior.

Breaking changes

• PATCH /v1/monitors/{id} operation identifier renamed from updateMonitor to UpdateMonitor. Generated clients may rename the corresponding method; raw HTTP callers are unaffected.
• PATCH /v1/monitors/{id} is now documented with Monitor-UpdateRequest and Monitor-Resource, and the MonitorV2PatchRequest schema was removed from the spec. The default (no-header) request and its 204 response do not change on the wire. Generated clients lose the MonitorV2PatchRequest model, so code that builds one for update needs to change. This breaks generated clients only, not the wire contract.
• PATCH /v1/monitors/{id} path parameter id is now modeled as a string instead of an integer. The URL value remains textual on the wire, but generated clients may need to change the parameter type.
• Dataset list CEL filters on a storage integration now use storageIntegration.record.name instead of storageIntegration.record.label. Callers that filter on record.label need to switch to record.name.

Deprecations

None.

Migration

1. Regenerate generated clients and update the update call:

- client.updateMonitor(41000123, monitorV2PatchRequest)
+ client.UpdateMonitor("41000123", updateRequest)   // Monitor-UpdateRequest

2. Update dataset filters that read a storage integration's label:

- storageIntegration != null && storageIntegration.record.label == "snowflake-prod"
+ storageIntegration != null && storageIntegration.record.name == "snowflake-prod"

3. To opt in to the versioned update, send Observe-Api-Version: 2026-10-06 once your account is enabled, and send only the fields you want to change.