fix(generated): Move organization connected-account operations onto Pipes

[workos-sdk-automation]

Summary

fix(pipes): Move organization connected-account operations onto Pipes

The previous regeneration exposed the organization connected-account endpoints on a standalone OrganizationsDataProviders resource. That was the wrong home (workos/openapi-spec#179 corrects the service ownership), and it never shipped in a release. The same five endpoints are now on the Pipes resource. Nothing was added to or removed from the API itself; only where the SDK exposes it changed.

Before (unreleased)	Now
client.organizations_data_providers.get_organization_connected_account	client.pipes.get_organization_connected_account
client.organizations_data_providers.create_organization_connected_account	client.pipes.create_organization_connected_account
client.organizations_data_providers.update_organization_connected_account	client.pipes.update_organization_connected_account
client.organizations_data_providers.delete_organization_connected_account	client.pipes.delete_organization_connected_account
client.organizations_data_providers.list_organization_data_providers	client.pipes.list_organization_data_providers

Method names are unchanged; only the accessor moved.

fix(multi_factor_auth): Change errors for endpoint POST /auth/factors/{id}/challenge

• Changed errors for endpoint POST /auth/factors/{id}/challenge.

Triggered by workos/openapi-spec@bfe7aed

BEGIN_COMMIT_OVERRIDE
fix(pipes): Move organization connected-account operations onto Pipes (#557)
fix(multi_factor_auth): Change errors for endpoint POST /auth/factors/{id}/challenge (#557)
END_COMMIT_OVERRIDE

[greptile-apps]

Confidence Score: 5/5

The code changes appear safe to merge, with only non-blocking release-note incompleteness remaining from the previous review.

Findings

1.  Release Note Omits Changes ▶

Fix with agent prompt

### Issue 1
.changelog-pending/2026-09-17T21-00-23-bfe7aedb3cf7296ffb6ead1e287e844186479702.md:5-6
The release note describes only the relocation of five operations, but this PR also adds the public fields `connection_owner`, `connection_role`, `account_identifier`, and `account_display_name`, and makes the existing `ownership` reader emit a deprecation warning. Please document these additions and the deprecation so consumers receive complete migration guidance instead of encountering an unannounced warning.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This PR moves the unreleased organization connected-account operations from the standalone OrganizationsDataProviders resource to Pipes while preserving their HTTP behavior and updates the generated models, RBI declarations, tests, manifest, and pending changelog accordingly.

• Removes the obsolete client accessor, generated service, model copies, RBI file, and tests for OrganizationsDataProviders.
• Exposes all five organization connected-account operations through client.pipes.
• Retains the associated models under the collapsed Pipes model directory.
• Updates pending release notes to document the new fields and operation location; the existing ownership deprecation remains undocumented.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    Client["WorkOS::Client"]
    Old["OrganizationsDataProviders<br/>(removed)"]
    Pipes["WorkOS::Pipes"]
    API["Organization connected-account API"]
    Models["Connected-account and data-provider models"]

    Client -. "old unreleased accessor removed" .-> Old
    Client --> Pipes
    Pipes --> API
    Pipes --> Models

Loading

_{Reviews (3) · Last reviewed commit: "chore: drop the redundant move entry fro..."}

[greptile-apps]

Release Note Omits Changes

The release note describes only the relocation of five operations, but this PR also adds the public fields connection_owner, connection_role, account_identifier, and account_display_name, and makes the existing ownership reader emit a deprecation warning. Please document these additions and the deprecation so consumers receive complete migration guidance instead of encountering an unannounced warning.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .changelog-pending/2026-09-17T21-00-23-bfe7aedb3cf7296ffb6ead1e287e844186479702.md
Line: 5-6

Comment:
**Release Note Omits Changes**

The release note describes only the relocation of five operations, but this PR also adds the public fields `connection_owner`, `connection_role`, `account_identifier`, and `account_display_name`, and makes the existing `ownership` reader emit a deprecation warning. Please document these additions and the deprecation so consumers receive complete migration guidance instead of encountering an unannounced warning.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!