Skip to content

Latest commit

 

History

History
266 lines (262 loc) · 96.9 KB

accepted-breaking-changes.md

File metadata and controls

266 lines (262 loc) · 96.9 KB

Accepted breaking changes

CI fails a pull request on any change to api/openapi.yaml that oasdiff calls breaking. A line here lets exactly one such change through: oasdiff matches a line by its method and path and the change's own words, so any other breaking change still fails. Add a line only for a change that takes nothing from a client, and say why on the line: the date, the change as oasdiff words it, and the reason.

Once the change is on the base branch, oasdiff no longer reports it and its line matches nothing.

CI also holds the spec to the last release's, with these same lines, except any that says "no release serves it": that reason is about the release, so it is checked against the release. Write it in those words when it is the reason, and the release run fails if the release does serve it.

  • 2026-11-14 GET /api/v2/organizations/{organizationId}/bots added the pattern ^[A-Za-z0-9_-]+$ to the query request parameter cursor. The server only issues cursors in URL-safe base64 and has always refused any other cursor with 400, so no request that worked stops working.
  • 2026-11-14 GET /api/v2/organizations/{organizationId}/reactions added the pattern ^[A-Za-z0-9_-]+$ to the query request parameter cursor. The same cursor, and the same refusal of any other.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/bots request property harness was restricted to a list of enum values. The server has always refused a harness outside OpenBot's harness list with 400; the enum is that list, and api/openapi-harnesses.test.ts keeps the two the same.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/capabilities/translate removed the enum constraint from the changes/items/capability response property for the response status 200. The operation was described today and no release serves it yet. When the model's changes don't check, they come back as written so the admin can see what failed, and a model can name a permission that isn't one; check says so.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/capabilities/translate the changes/items/scopeId response property's maxLength was unset from 200 for the response status 200. The same changes, as the model wrote them.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/capabilities/translate the changes/items/scopeId response's property pattern ^[^\x00]*$ was removed for the status 200. The same changes, as the model wrote them.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/network-policies/translate removed the enum constraint from the rules/items/type response property for the response status 200. The operation was described today and no release serves it yet. When the model's entries don't parse, they come back as written so the admin can fix them; check says which failed.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/network-policies/translate the rules/items/ports response property's maxLength was unset from 100 for the response status 200. The same entries, as the model wrote them.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/network-policies/translate the rules/items/value response property's maxLength was unset from 253 for the response status 200. The same entries, as the model wrote them.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/network-policies/translate the rules/items/value response property's minLength was unset from 1 for the response status 200. The same entries, as the model wrote them.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/people/{personId}/stop-computers removed the required property failed/items/botId from the response with the 200 status. The operation was described today and no release serves it yet. A computer that would not stop is a person's own or a Bot's, so it is named as stopped names it, in computer; the server has always answered that way.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/capabilities/preview the changes/items/capability request property's maxLength was set to 100. The property was a list of the permission ids and is now any text the answer's check judges; every id the list held is shorter than that, so nothing accepted before is refused.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/capabilities/preview added the pattern ^[^\x00]*$ to the request property changes/items/capability. The same property; no permission id holds a NUL.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/capabilities/preview added the new member enum value to the people/items/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/capabilities/preview added the new owner enum value to the people/items/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 GET /api/v2/organizations/{organizationId}/people added the new member enum value to the people/items/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 GET /api/v2/organizations/{organizationId}/people added the new owner enum value to the people/items/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 GET /api/v2/organizations/{organizationId}/people/{personId} added the new member enum value to the person/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 GET /api/v2/organizations/{organizationId}/people/{personId} added the new owner enum value to the person/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 PATCH /api/v2/organizations/{organizationId}/people/{personId} removed the enum value user of the request property role. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 PATCH /api/v2/organizations/{organizationId}/people/{personId} added the new member enum value to the person/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 PATCH /api/v2/organizations/{organizationId}/people/{personId} added the new owner enum value to the person/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/people/{personId}/restore-access added the new member enum value to the person/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/people/{personId}/restore-access added the new owner enum value to the person/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/people/{personId}/revoke-access added the new member enum value to the person/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 POST /api/v2/organizations/{organizationId}/people/{personId}/revoke-access added the new owner enum value to the person/role response property for the response status 200. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-14 PATCH /api/v2/organizations/{organizationId}/capabilities/{capabilityId} removed the request property roles/user. Renamed before any release to the organisation-member roles: owner, admin and member, where a person was admin or user.
  • 2026-11-15 POST /api/v2/organizations/{organizationId}/members api removed without deprecation. Adding somebody who already had an account, by email, was described before any release and no release serves it. People join an organization by invitation: POST /api/v2/organizations/{organizationId}/invitations, which the person accepts.
  • 2026-11-15 PUT /api/v2/organizations/{organizationId}/apps/{appId}/account-mode added the new team enum value to the bots/items/approval/members/items/kind response property for the response status 200. A shared account's audience can now name a team by id beside a person and a directory group; nothing is taken from a client, and one written before teams never sent or approved a team.
  • 2026-11-15 GET /api/v2/organizations/{organizationId}/bots/{botId}/shared-use added the new team enum value to the apps/items/approval/oneOf[#/components/schemas/SharedUseApproval]/members/items/kind response property for the response status 200 (shared schema: SharedUseApproval, also at apps/items/needed/members/items/kind, pending/items/current/oneOf[#/components/schemas/SharedUseApproval]/members/items/kind and 1 more). A shared account's audience can now name a team by id beside a person and a directory group; nothing is taken from a client, and one written before teams never sent or approved a team.
  • 2026-11-15 POST /api/v2/organizations/{organizationId}/capabilities/batch-update added the new team enum value to the saved/items/scopeKind response property for the response status 200. A permission switch can now be set for a team by id, beside the organization, a role and a directory group; a client that never set one never reads one.
  • 2026-11-15 POST /api/v2/organizations/{organizationId}/capabilities/preview added the new team enum value to the people/items/capabilities/items/after/decidedBy response property for the response status 200 (shared schema: CapabilityAnswer, also at people/items/capabilities/items/before/decidedBy). A team's switch can now be the one that decides a person's permission, as a directory group's can.
  • 2026-11-15 POST /api/v2/organizations/{organizationId}/capabilities/translate added the new team enum value to the changes/items/scopeKind response property for the response status 200. A permission switch can now be set for a team by id, beside the organization, a role and a directory group; a client that never set one never reads one.
  • 2026-11-15 GET /api/v2/organizations/{organizationId}/network-policies added the new team enum value to the networkPolicies/items/scopeKind response property for the response status 200. A network policy can now be set for a team by id, beside the organization and a directory group; a client that never set one never reads one.
  • 2026-11-15 PUT /api/v2/organizations/{organizationId}/network-policies/{networkPolicyId} added the new team enum value to the scopeKind response property for the response status 200. A network policy can now be set for a team by id, beside the organization and a directory group; a client that never set one never reads one.
  • 2026-11-15 GET /api/v2/organizations/{organizationId}/shared-use-requests added the new team enum value to the sharedUseRequests/items/current/oneOf[#/components/schemas/SharedUseApproval]/members/items/kind response property for the response status 200 (shared schema: SharedUseApproval, also at sharedUseRequests/items/proposed/members/items/kind). A shared account's audience can now name a team by id beside a person and a directory group; nothing is taken from a client, and one written before teams never sent or approved a team.
  • 2026-11-15 POST /api/v2/organizations/{organizationId}/shared-use-requests/{sharedUseRequestId}/approve added the new team enum value to the current/oneOf[#/components/schemas/SharedUseApproval]/members/items/kind response property for the response status 200 (shared schema: SharedUseApproval, also at proposed/members/items/kind). A shared account's audience can now name a team by id beside a person and a directory group; nothing is taken from a client, and one written before teams never sent or approved a team.
  • 2026-11-15 POST /api/v2/organizations/{organizationId}/shared-use-requests/{sharedUseRequestId}/decline added the new team enum value to the current/oneOf[#/components/schemas/SharedUseApproval]/members/items/kind response property for the response status 200 (shared schema: SharedUseApproval, also at proposed/members/items/kind). A shared account's audience can now name a team by id beside a person and a directory group; nothing is taken from a client, and one written before teams never sent or approved a team.
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/app-access-requests removed the enum constraint from the appAccessRequests/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/app-access-requests removed the enum constraint from the status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/app-access-requests/{appAccessRequestId}/approve removed the enum constraint from the appAccessRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/app-access-requests/{appAccessRequestId}/dismiss removed the enum constraint from the status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/bots/{botId}/apps/{appId}/approve removed the enum constraint from the appAccessRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/bots/{botId}/shared-use removed the enum constraint from the pending/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/capabilities/preview removed the enum constraint from the people/items/capabilities/items/after/decidedBy response property for the response status 200 (shared schema: CapabilityAnswer, also at people/items/capabilities/items/before/decidedBy). Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/capabilities/preview removed the enum constraint from the people/items/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/check-in-items removed the enum constraint from the checkInItems/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/check-in-items/{checkInItemId}/dismiss removed the enum constraint from the checkInItem/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/check-in-items/{checkInItemId}/start removed the enum constraint from the checkInItem/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/check-ins removed the enum constraint from the checkIns/items/lastStatus response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/check-ins removed the enum constraint from the checkIn/lastStatus response property for the response status 201. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 PATCH /api/v2/organizations/{organizationId}/check-ins/{checkInId} removed the enum constraint from the checkIn/lastStatus response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/reset removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/stop removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/update removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId} removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId} removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId} removed the enum constraint from the state response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/click removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/click removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/click removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/click removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/control removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/control removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/control removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/control removed the enum constraint from the request/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/cancel removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/cancel removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/cancel removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/cancel removed the enum constraint from the request/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/release removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/release removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/release removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/release removed the enum constraint from the request/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/request removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/request removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/request removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/request removed the enum constraint from the request/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/secret removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/secret removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/secret removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/secret removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/secret removed the enum constraint from the request/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/take removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/take removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/take removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/control/take removed the enum constraint from the request/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/exec removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/exec removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/exec removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/exec removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/list removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/list removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/list removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/list removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/read removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/read removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/read removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/read removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/write removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/write removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/write removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/files/write removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/human-input/secret removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/human-input/secret removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/human-input/secret removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/human-input/secret removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/human-input/{kind} removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/human-input/{kind} removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/human-input/{kind} removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/key removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/key removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/key removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/key removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/navigate removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/navigate removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/navigate removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/navigate removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/page removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/page removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/page removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/page-frames/{toolCallId} removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/screenshot removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/screenshot removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/computers/{botId}/screenshot removed the enum constraint from the oneOf[#/components/schemas/ComputerNotReady]/state response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/scroll removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/scroll removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/scroll removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/scroll removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/snapshot removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/snapshot removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/snapshot removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/type removed the enum constraint from the handoff/status response property for the response status 403. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/type removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/type removed the enum constraint from the handoff/status response property for the response status 409. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/type removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/wake removed the enum constraint from the handoff/status response property for the response status 404. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/wake removed the enum constraint from the handoff/status response property for the response status 503. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/computers/{botId}/wake removed the enum constraint from the state response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/conversations/{conversationId}/messages removed the enum constraint from the messages/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/goals removed the enum constraint from the goals/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/goals removed the enum constraint from the goal/status response property for the response status 201. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 PATCH /api/v2/organizations/{organizationId}/goals/{goalId} removed the enum constraint from the goal/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/goals/{goalId}/complete removed the enum constraint from the goal/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/goals/{goalId}/pause removed the enum constraint from the goal/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/goals/{goalId}/resume removed the enum constraint from the goal/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/goals/{goalId}/runs removed the enum constraint from the runs/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/invitations removed the enum constraint from the invitations/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/invitations removed the enum constraint from the invitation/status response property for the response status 201. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/members removed the enum constraint from the members/items/assignableRoles/items/ response property for the response status 200 (shared schema: PersonRoleAnswer, also at members/items/assignableRoles/items, members/items/role). Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 PATCH /api/v2/organizations/{organizationId}/members/{personId} removed the enum constraint from the member/assignableRoles/items/ response property for the response status 200 (shared schema: PersonRoleAnswer, also at member/assignableRoles/items, member/role). Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/network-policies removed the enum constraint from the networkPolicies/items/scopeKind response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 PUT /api/v2/organizations/{organizationId}/network-policies/{networkPolicyId} removed the enum constraint from the scopeKind response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people removed the enum constraint from the people/items/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId} removed the enum constraint from the person/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 PATCH /api/v2/organizations/{organizationId}/people/{personId} removed the enum constraint from the person/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/approvals removed the enum constraint from the approvals/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/approvals/{approvalId}/decide removed the enum constraint from the status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/deliveries removed the enum constraint from the deliveries/items/state response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/learning-proposals removed the enum constraint from the skills/items/proposal/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/learning-proposals/{proposalId} removed the enum constraint from the status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/learning-review removed the enum constraint from the spaces/items/latestRun/oneOf[#/components/schemas/LearningRun]/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/learning-review removed the enum constraint from the spaces/items/proposals/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/learning-runs removed the enum constraint from the status response property for the response status 202. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/linked-accounts removed the enum constraint from the linkedAccounts/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/memory-sources removed the enum constraint from the sources/items/syncStatus response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/memory-sources removed the enum constraint from the source/syncStatus response property for the response status 201. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 PATCH /api/v2/organizations/{organizationId}/people/{personId}/memory-sources/{memorySourceId} removed the enum constraint from the syncStatus response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/memory-sources/{memorySourceId}/sync removed the enum constraint from the source/syncStatus response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/restore-access removed the enum constraint from the person/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/revoke-access removed the enum constraint from the person/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests removed the enum constraint from the signInRequests/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests removed the enum constraint from the signInRequest/status response property for the response status 201. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests/{signInRequestId} removed the enum constraint from the signInRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests/{signInRequestId}/cancel removed the enum constraint from the signInRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests/{signInRequestId}/code removed the enum constraint from the signInRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests/{signInRequestId}/finish removed the enum constraint from the signInRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests/{signInRequestId}/submit removed the enum constraint from the signInRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests/{signInRequestId}/take-over removed the enum constraint from the signInRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/people/{personId}/sign-in-requests/{signInRequestId}/use-saved removed the enum constraint from the signInRequest/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/personal-learning-proposals removed the enum constraint from the people/items/proposals/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 PATCH /api/v2/organizations/{organizationId}/profile removed the enum constraint from the organization/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/routines removed the enum constraint from the routines/items/lastRun/oneOf[#/components/schemas/RoutineLastRun]/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/routines removed the enum constraint from the routine/lastRun/oneOf[#/components/schemas/RoutineLastRun]/status response property for the response status 201. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 PATCH /api/v2/organizations/{organizationId}/routines/{routineId} removed the enum constraint from the routine/lastRun/oneOf[#/components/schemas/RoutineLastRun]/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/routines/{routineId}/runs removed the enum constraint from the runs/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/settings/learning/proposals removed the enum constraint from the proposals/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/settings/learning/proposals/{proposalId} removed the enum constraint from the status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/settings/learning/runs removed the enum constraint from the runs/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/settings/learning/runs removed the enum constraint from the status response property for the response status 202. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/shared-use-requests removed the enum constraint from the sharedUseRequests/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/shared-use-requests/{sharedUseRequestId}/approve removed the enum constraint from the status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/shared-use-requests/{sharedUseRequestId}/decline removed the enum constraint from the status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/tasks removed the enum constraint from the tasks/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/organizations/{organizationId}/tasks/{taskId} removed the enum constraint from the task/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/tasks/{taskId}/reopen removed the enum constraint from the task/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/tasks/{taskId}/resolve removed the enum constraint from the task/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/tasks/{taskId}/retry removed the enum constraint from the task/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/organizations/{organizationId}/tasks/{taskId}/stop removed the enum constraint from the task/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/people/me/invitations removed the enum constraint from the invitations/items/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/people/me/invitations/{invitationId} removed the enum constraint from the invitation/status response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/people/me/invitations/{invitationId}/accept removed the enum constraint from the organization/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 GET /api/v2/people/me/organizations removed the enum constraint from the organizations/items/role response property for the response status 200. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-17 POST /api/v2/people/me/organizations removed the enum constraint from the organization/role response property for the response status 201. Declared open with x-extensible-enum, with the same values: the server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-18 GET /api/v2/organizations/{organizationId}/members removed the enum constraint from the members/items/assignableRoles/items response property for the response status 200 (shared schema: PersonRoleAnswer, also at members/items/role). Against 1.1.0, as the last release run words it: the role a member holds and the roles they may be given, declared open with x-extensible-enum with the same values. The server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/members/{personId} removed the enum constraint from the member/assignableRoles/items response property for the response status 200 (shared schema: PersonRoleAnswer, also at member/role). Against 1.1.0, as the last release run words it: the role a member holds and the roles they may be given, declared open with x-extensible-enum with the same values. The server sends nothing it did not send before, and every client reads a value it doesn't know (api/README.md, Enums that grow).
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/approval-rules changed the pattern of the request property botId from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/approval-rules changed the pattern of the request property effect from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/approval-rules changed the pattern of the request property scope from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/approval-rules changed the pattern of the request property toolRef from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/approval-rules/batch-create changed the pattern of the request property authoring/text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/approval-rules/translate changed the pattern of the request property text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/approval-rules/{approvalRuleId} changed the pattern of the request property botId from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ (shared schema: ApprovalRulePattern, also at effect, scope and 1 more). The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/bots/{botId}/grants/batch-update changed the pattern of the request property authoring/text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/bots/{botId}/grants/translate changed the pattern of the request property text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/bots/{botId}/report-decline changed the pattern of the request property reason from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PUT /api/v2/organizations/{organizationId}/boundaries changed the pattern of the request property authoring/text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PUT /api/v2/organizations/{organizationId}/boundaries changed the pattern of the request property labels/additionalProperties/name from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/boundaries/replay changed the pattern of the request property boundaries/labels/additionalProperties/name from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/boundaries/translate changed the pattern of the request property text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/capabilities/batch-update changed the pattern of the request property authoring/text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/capabilities/translate changed the pattern of the request property text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/capabilities/{capabilityId} changed the pattern of the request property groups/propertyNames from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/capabilities/{capabilityId} changed the pattern of the request property teams/propertyNames from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/identity-providers changed the pattern of the request property oneOf[#/components/schemas/OidcIdentityProviderRequest]/clientId from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ (shared schema: IdentityProviderText, also at oneOf[#/components/schemas/OidcIdentityProviderRequest]/clientSecret). The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/identity-providers changed the pattern of the request property oneOf[#/components/schemas/SamlIdentityProviderRequest]/domain from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ (shared schema: IdentityProviderDomains, also at oneOf[#/components/schemas/OidcIdentityProviderRequest]/domain). The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/identity-providers changed the pattern of the request property oneOf[#/components/schemas/SamlIdentityProviderRequest]/id from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ (shared schema: NewIdentityProviderId, also at oneOf[#/components/schemas/OidcIdentityProviderRequest]/id). The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/identity-providers changed the pattern of the request property oneOf[#/components/schemas/SamlIdentityProviderRequest]/metadata from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/network-policies/translate changed the pattern of the request property text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PUT /api/v2/organizations/{organizationId}/network-policies/{networkPolicyId} changed the pattern of the request property authoring/text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/people/{personId}/approval-rules changed the pattern of the request property botId from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/people/{personId}/approval-rules changed the pattern of the request property effect from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/people/{personId}/approval-rules changed the pattern of the request property scope from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/people/{personId}/approval-rules changed the pattern of the request property toolRef from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/people/{personId}/approval-rules/{approvalRuleId} changed the pattern of the request property botId from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ (shared schema: ApprovalRulePattern, also at effect, scope and 1 more). The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/people/{personId}/questions/{questionId}/respond changed the pattern of the request property response from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/profile changed the pattern of the request property name from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PUT /api/v2/organizations/{organizationId}/reviewer-guidance changed the pattern of the request property text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/reviewer-guidance/check changed the pattern of the request property text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/reviewer-guidance/replay changed the pattern of the request property text from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 GET /api/v2/organizations/{organizationId}/settings the mcpAllowlist/servers/items response's property pattern was changed from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ for the status 200 (shared schema: AllowlistEntry, also at modelAllowlist/models/items). The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/settings changed the pattern of the request property mcpAllowlist/servers/items from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ (shared schema: AllowlistEntry, also at modelAllowlist/models/items). The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/settings the mcpAllowlist/servers/items response's property pattern was changed from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ for the status 200 (shared schema: AllowlistEntry, also at modelAllowlist/models/items). The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/teams changed the pattern of the request property name from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/teams/{teamId} changed the pattern of the request property name from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/organizations/{organizationId}/what-if/ask changed the pattern of the request property question from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 POST /api/v2/people/me/organizations changed the pattern of the request property name from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The pattern now refuses NUL in the one character it requires as well as everywhere else, as the server always has ("That text has a character OpenBot can't keep"): nothing it accepted before is refused, and nothing it sends has changed.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/capabilities/{capabilityId} changed the pattern of the request property groups/propertyNames/ from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The same change as worded by oasdiff 1.34: NUL refused in the one required character as everywhere else, as the server always has.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/capabilities/{capabilityId} changed the pattern of the request property teams/propertyNames/ from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$. The same change as worded by oasdiff 1.34: NUL refused in the one required character as everywhere else, as the server always has.
  • 2026-11-18 GET /api/v2/organizations/{organizationId}/settings the mcpAllowlist/servers/items/ response's property pattern was changed from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ for the status 200 (shared schema: AllowlistEntry, also at mcpAllowlist/servers/items, modelAllowlist/models/items). The same change as worded by oasdiff 1.34: NUL refused in the one required character as everywhere else, as the server always has.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/settings changed the pattern of the request property mcpAllowlist/servers/items/ from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ (shared schema: AllowlistEntry, also at mcpAllowlist/servers/items, modelAllowlist/models/items). The same change as worded by oasdiff 1.34: NUL refused in the one required character as everywhere else, as the server always has.
  • 2026-11-18 PATCH /api/v2/organizations/{organizationId}/settings the mcpAllowlist/servers/items/ response's property pattern was changed from ^[^\x00]*\S[^\x00]*$ to ^[^\x00]*[^\s\x00][^\x00]*$ for the status 200 (shared schema: AllowlistEntry, also at mcpAllowlist/servers/items, modelAllowlist/models/items). The same change as worded by oasdiff 1.34: NUL refused in the one required character as everywhere else, as the server always has.