Security requirements changed for PATCH /organizations/{organization_id}

What changed

Security requirements changed for PATCH /organizations/{organization_id} Affected surface: PATCH /organizations/{organization_id}. Detected at Tue, 24 Sep 2024 10:29:04 UTC UTC.

Diff

{
  "current_value": [
    {
      "OAuth2BearerToken": [
        "organization--my:rw"
      ]
    },
    {
      "PersonalAccessToken": [
        "organization--my:rw"
      ]
    }
  ],
  "path": "PATCH /organizations/{organization_id}",
  "previous_value": [
    {
      "OAuth2BearerToken": [
        "organization--my:rw"
      ]
    },
    {
      "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.