feat(generated): Changes to pipes

[workos-sdk-automation]

Summary

feat(pipes): Change Pipes API surface

• SDK surface change: Required parameter "user_id" added to "Pipes.create_organization_connected_account".
• SDK surface change: Required parameter "user_id" added to "Pipes.update_organization_connected_account".

Triggered by workos/openapi-spec@0b0182d

BEGIN_COMMIT_OVERRIDE
feat(pipes): Change Pipes API surface (#561)
END_COMMIT_OVERRIDE

[greptile-apps]

Confidence Score: 4/5

[Medium risk] Regenerated data integration API models and endpoints.

The PR is not yet safe to merge because the Pipes update signatures still reject supported connection-selection keywords for typed callers.

Findings

1.  Update signatures omit selection keywords ▶
2.  Creation tests ignore request bodies ▶

Fix with agent prompt

### Issue 1
rbi/workos/pipes.rbi:undefined-94
When a Sorbet-typed caller passes `connected_account_id` or `connection_intent` to reauthorize a specific API-key connection, this signature rejects the call even though the Ruby method accepts and sends both values. The client-credentials update signature has the same mismatch, so typed callers cannot select a connection through either method.

### Issue 2
test/workos/test_pipes.rb:49-53
This test checks only the URL and that a result is returned. It would pass if the new API-key creation method omitted `user_id`, the secret, or the required `connection_intent` from its JSON body. The new client-credentials test has the same gap. Checking the outgoing bodies would catch mistakes in these new request contracts.

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

The PR regenerates the Pipes SDK surface for connected-account creation, updates, and credential models. Since the previous review, only the pending changelog’s title marker changed.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Caller[Ruby application] --> Pipes[Pipes SDK]
  Pipes --> Create[Create connected account]
  Pipes --> Update[Update or reauthorize connection]
  Create --> API[WorkOS Pipes API]
  Update --> API

Loading

_{Reviews (2) · Last reviewed commit: "chore(generated): drop breaking marker f..."}

[greptile-apps]

Update signatures omit selection keywords
When a Sorbet-typed caller passes connected_account_id or connection_intent to reauthorize a specific API-key connection, this signature rejects the call even though the Ruby method accepts and sends both values. The client-credentials update signature has the same mismatch, so typed callers cannot select a connection through either method.

Knowledge Base Used: Connect, Pipes, and Admin Portal

Prompt To Fix With AI

This is a comment left during a code review.
Path: rbi/workos/pipes.rbi
Line: 94

Comment:
**Update signatures omit selection keywords**
When a Sorbet-typed caller passes `connected_account_id` or `connection_intent` to reauthorize a specific API-key connection, this signature rejects the call even though the Ruby method accepts and sends both values. The client-credentials update signature has the same mismatch, so typed callers cannot select a connection through either method.

**Knowledge Base Used:** [Connect, Pipes, and Admin Portal](https://app.greptile.com/workos/-/custom-context/knowledge-base/workos/workos-ruby/-/docs/connect-pipes-and-admin-portal.md)

---

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

[greptile-apps]

Creation tests ignore request bodies
This test checks only the URL and that a result is returned. It would pass if the new API-key creation method omitted user_id, the secret, or the required connection_intent from its JSON body. The new client-credentials test has the same gap. Checking the outgoing bodies would catch mistakes in these new request contracts.

Prompt To Fix With AI

This is a comment left during a code review.
Path: test/workos/test_pipes.rb
Line: 49-53

Comment:
**Creation tests ignore request bodies**
This test checks only the URL and that a result is returned. It would pass if the new API-key creation method omitted `user_id`, the secret, or the required `connection_intent` from its JSON body. The new client-credentials test has the same gap. Checking the outgoing bodies would catch mistakes in these new request contracts.

---

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!