Security requirements changed for PUT /v1/dev_resources

What changed

Security requirements changed for PUT /v1/dev_resources Affected surface: PUT /v1/dev_resources. Detected at Thu, 07 May 2026 00:09:05 UTC UTC.

Diff

{
  "current_value": [
    {
      "OAuth2": [
        "file_dev_resources:write"
      ]
    },
    {
      "PersonalAccessToken": null
    },
    {
      "PlanAccessToken": null
    }
  ],
  "path": "PUT /v1/dev_resources",
  "previous_value": [
    {
      "OAuth2": [
        "file_dev_resources:write"
      ]
    },
    {
      "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.