Security requirements changed for GET /workspaces/{workspace_gid}/typeahead

What changed

Security requirements changed for GET /workspaces/{workspace_gid}/typeahead Affected surface: GET /workspaces/{workspace_gid}/typeahead. Detected at Mon, 09 Mar 2026 23:11:41 UTC UTC.

Diff

{
  "current_value": [
    {
      "oauth2": [
        "workspaces.typeahead:read"
      ]
    },
    {
      "personalAccessToken": null
    }
  ],
  "path": "GET /workspaces/{workspace_gid}/typeahead",
  "previous_value": [
    {
      "oauth2": [
        "workspace.typeahead:read"
      ]
    },
    {
      "personalAccessToken": null
    }
  ]
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Recommended action

Re-check your auth setup against the provider's current docs. Auth changes typically require config updates, not code changes.