feat(generated): Authorization (batch c64ce1e7)

[workos-sdk-automation]

Summary

Regenerated SDK from spec changes.

Triggered by workos/openapi-spec@e2873c2

[greptile-apps]

Confidence Score: 4/5

The PR should not merge until the existing workos.pipes.models.ConnectedAccountInput import path is restored.

Findings

1.  Pipes model import removed ▶
2.  Wildcard imports expose unrelated names ▶
3.  Populated source group remains untested ▶

Fix with agent prompt

### Issue 1
src/workos/pipes/models/__init__.py:3
Callers that use `from workos.pipes.models import ConnectedAccountInput` could import it before this change. The re-export is now gone, so that import raises `ImportError`. Please restore the existing import path.

### Issue 2
src/workos/common/models/__init__.py:57
The new wildcard imports also export names such as `Enum`, `Literal`, and `TypeAlias` from model modules. The wildcard import in `workos.common` passes those names on again. This makes the public namespace harder to use and maintain; explicit model exports would keep unrelated names out.

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!

### Issue 3
tests/test_authorization_models_round_trip.py:529-535
This test round-trips the group model by itself, but every source and role-assignment fixture has `group: null`. A test with a populated group nested in a role assignment would cover the new deserialization and serialization path, so a regression there does not go unnoticed.

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 regeneration adds a nullable group to authorization role-assignment sources and updates model exports and fixtures.

• The new group model and its standalone round trip are covered, but a populated group nested in a role assignment is not.
• The export changes remove an existing Pipes import path and broaden common-model wildcard exports.

_{Reviews (1) · Last reviewed commit: "chore(generated): add release notes frag..."}

[greptile-apps]

Pipes model import removed
Callers that use from workos.pipes.models import ConnectedAccountInput could import it before this change. The re-export is now gone, so that import raises ImportError. Please restore the existing import path.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/workos/pipes/models/__init__.py
Line: 3

Comment:
**Pipes model import removed**
Callers that use `from workos.pipes.models import ConnectedAccountInput` could import it before this change. The re-export is now gone, so that import raises `ImportError`. Please restore the existing import path.

---

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

[greptile-apps]

Wildcard imports expose unrelated names
The new wildcard imports also export names such as Enum, Literal, and TypeAlias from model modules. The wildcard import in workos.common passes those names on again. This makes the public namespace harder to use and maintain; explicit model exports would keep unrelated names out.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/workos/common/models/__init__.py
Line: 57

Comment:
**Wildcard imports expose unrelated names**
The new wildcard imports also export names such as `Enum`, `Literal`, and `TypeAlias` from model modules. The wildcard import in `workos.common` passes those names on again. This makes the public namespace harder to use and maintain; explicit model exports would keep unrelated names out.

---

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!

[greptile-apps]

Populated source group remains untested
This test round-trips the group model by itself, but every source and role-assignment fixture has group: null. A test with a populated group nested in a role assignment would cover the new deserialization and serialization path, so a regression there does not go unnoticed.

Prompt To Fix With AI

This is a comment left during a code review.
Path: tests/test_authorization_models_round_trip.py
Line: 529-535

Comment:
**Populated source group remains untested**
This test round-trips the group model by itself, but every source and role-assignment fixture has `group: null`. A test with a populated group nested in a role assignment would cover the new deserialization and serialization path, so a regression there does not go unnoticed.

---

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!