feat(generated): Pipes, PipesProvider, UserManagement (batch 6c21f6dc)

[workos-sdk-automation]

Summary

Regenerated SDK from spec changes.

Triggered by workos/openapi-spec@72f2c0b

[greptile-apps]

Positional argument binding breaks

When existing consumers pass credentials or request options positionally, the new config parameter captures the former argument position with an incompatible ?array type, causing previously valid calls to throw TypeError. The same breaking insertion occurs in authorizeDataIntegration and PipesProvider::updateOrganizationDataIntegrationConfiguration.

Knowledge Base Used: ClientApi and Pipes services

Prompt To Fix With AI

This is a comment left during a code review.
Path: lib/Service/Pipes.php
Line: 78

Comment:
**Positional argument binding breaks**

When existing consumers pass credentials or request options positionally, the new `config` parameter captures the former argument position with an incompatible `?array` type, causing previously valid calls to throw `TypeError`. The same breaking insertion occurs in `authorizeDataIntegration` and `PipesProvider::updateOrganizationDataIntegrationConfiguration`.

**Knowledge Base Used:** [ClientApi and Pipes services](https://app.greptile.com/workos/-/custom-context/knowledge-base/workos/workos-php/-/docs/client-api-and-pipes.md)

---

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

[greptile-apps]

Greptile Summary

Regenerates the Pipes SDK models and services for provider configuration and client-credentials response values.

• Adds provider-specific config fields to integration, authorization, and organization-configuration request/response models.
• Adds client_credentials to returned authentication-method values while introducing a creation-specific authentication-method enum.
• Updates generated fixtures, manifest metadata, and synchronization metadata.

Confidence Score: 3/5

The PR should not merge until the new config parameters stop rebinding previously valid positional calls.

Three public service signatures insert config before existing typed arguments, causing established positional call shapes to fail with TypeError before sending their requests.

Files Needing Attention: lib/Service/Pipes.php and lib/Service/PipesProvider.php

Important Files Changed

Filename	Overview
lib/Service/Pipes.php	Adds config request parameters to integration creation and authorization, but inserts them before existing positional parameters and breaks compatible calls.
lib/Service/PipesProvider.php	Adds organization-level config passthrough while shifting the existing positional RequestOptions argument.
lib/Resource/DataIntegration.php	Adds the required provider config field to DataIntegration deserialization and serialization.
lib/Resource/DataIntegrationConfigurationResponse.php	Adds the required effective organization config field to configuration responses.
lib/Resource/DataIntegrationAuthMethods.php	Adds support for deserializing the client_credentials authentication method.

Prompt To Fix All With AI

### Issue 1
lib/Service/Pipes.php:78
**Config insertion breaks positional calls**

When existing consumers pass credentials or request options positionally, the new `config` parameter captures the value intended for the former parameter, causing PHP to throw a `TypeError` before the API request is sent. The same parameter shift affects `authorizeDataIntegration` and `PipesProvider::updateOrganizationDataIntegrationConfiguration`.

---

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

_{Reviews (2): Last reviewed commit: "chore(generated): add release notes frag..." | Re-trigger Greptile}

[greptile-apps]

Config insertion breaks positional calls

When existing consumers pass credentials or request options positionally, the new config parameter captures the value intended for the former parameter, causing PHP to throw a TypeError before the API request is sent. The same parameter shift affects authorizeDataIntegration and PipesProvider::updateOrganizationDataIntegrationConfiguration.

Knowledge Base Used: ClientApi and Pipes services

Prompt To Fix With AI

This is a comment left during a code review.
Path: lib/Service/Pipes.php
Line: 78

Comment:
**Config insertion breaks positional calls**

When existing consumers pass credentials or request options positionally, the new `config` parameter captures the value intended for the former parameter, causing PHP to throw a `TypeError` before the API request is sent. The same parameter shift affects `authorizeDataIntegration` and `PipesProvider::updateOrganizationDataIntegrationConfiguration`.

**Knowledge Base Used:** [ClientApi and Pipes services](https://app.greptile.com/workos/-/custom-context/knowledge-base/workos/workos-php/-/docs/client-api-and-pipes.md)

---

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