chore(main): release 10.0.0

[workos-sdk-automation]

🤖 I have created a release beep boop

10.0.0 (2026-07-21)

⚠ BREAKING CHANGES

• authorization: SDK surface change: Symbol "PermissionCreatedData" was removed (#695)
• connect: SDK surface change: Parameter type changed for "description" on "Connect.update_application" (#695)
• groups: SDK surface change: Parameter type changed for "description" on "Groups.create_organization_group" (#695)
• organizations: SDK surface change: Parameter type changed for "metadata" on "Organizations.create_organization" (#695)
• pipes: SDK surface change: Parameter type changed for "description" on "Pipes.create_data_integration" (#695)
• user_management: SDK surface change: Parameter type changed for "first_name" on "UserManagement.create_user" (#695)
• vault: SDK surface change: Parameter type changed for "version_check" on "Vault.update_kv" (#695)
• widgets: SDK surface change: Parameter type changed for "organization_id" on "Widgets.create_token" (#695)
• api_keys: SDK surface change: Parameter type changed for "expires_at" on "ApiKeys.create_api_key_expire" (#695)

Features

• Add NOT_GIVEN sentinel for nullable optional params (#694) (3b9a2cb)
• api_keys: SDK surface change: Parameter type changed for "expires_at" on "ApiKeys.create_api_key_expire" (#695) (a74e691)
• authorization: SDK surface change: Symbol "PermissionCreatedData" was removed (#695) (a74e691)
• connect: SDK surface change: Parameter type changed for "description" on "Connect.update_application" (#695) (a74e691)
• generated: AuditLogs (batch 56391ebd) (#690) (b1d3352)
• groups: SDK surface change: Parameter type changed for "description" on "Groups.create_organization_group" (#695) (a74e691)
• organizations: SDK surface change: Parameter type changed for "metadata" on "Organizations.create_organization" (#695) (a74e691)
• pipes: SDK surface change: Parameter type changed for "description" on "Pipes.create_data_integration" (#695) (a74e691)
• user_management: SDK surface change: Parameter type changed for "first_name" on "UserManagement.create_user" (#695) (a74e691)
• vault: SDK surface change: Parameter type changed for "version_check" on "Vault.update_kv" (#695) (a74e691)
• widgets: SDK surface change: Parameter type changed for "organization_id" on "Widgets.create_token" (#695) (a74e691)

Documentation

• clarify Idempotency-Key is only honored on audit log event creation (#692) (15003c0)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This is an automated Release Please PR bumping the workos-python SDK from v9.1.0 to v10.0.0, incorporating several features and breaking API surface changes introduced in prior merged PRs.

• Version bump: pyproject.toml, uv.lock, and .release-please-manifest.json are all updated from 9.1.0 to 10.0.0.
• CHANGELOG.md: The two pending changelog files (for PRs feat(generated): AuditLogs (batch 56391ebd) #690 and feat(generated)!: SDK surface change: Parameter type changed for "expires_at" on "ApiKeys.create_api_key_expire" (+8 more) #695) are deleted and their content is merged into CHANGELOG.md under the new 10.0.0 entry; however, the ### ⚠ BREAKING CHANGES section present in the Release Please PR description is absent from the committed file.
• Breaking changes included: 9 breaking API surface changes (symbol removal and parameter type changes across multiple services) plus the NOT_GIVEN sentinel addition from feat: Add NOT_GIVEN sentinel for nullable optional params #694.

Confidence Score: 4/5

Safe to merge for the version bump itself, but CHANGELOG.md will not document the 9 breaking API changes that motivated the major version increment.

All version artifacts (pyproject.toml, uv.lock, manifest) are consistent with 10.0.0. CHANGELOG.md is missing the breaking-changes section that Release Please generated for the PR description — downstream consumers relying solely on the file will not see that PermissionCreatedData was removed or that parameter types changed across eight SDK methods.

CHANGELOG.md — the 10.0.0 entry needs a ### ⚠ BREAKING CHANGES section listing the 9 breaking changes from PR #695.

Important Files Changed

Filename	Overview
CHANGELOG.md	10.0.0 entry added with Features and Documentation sections, but the ### ⚠ BREAKING CHANGES section present in the Release Please PR description is absent from the committed file
pyproject.toml	Version bumped from 9.1.0 to 10.0.0; no other changes
.release-please-manifest.json	Version manifest updated from 9.1.0 to 10.0.0
uv.lock	Lock file updated to reflect the new workos package version 10.0.0
.changelog-pending/2026-07-20T17-46-04-be67bca7f0a48ba858376717a86d7809a41f9786.md	Pending changelog entry for #690 deleted after being merged into CHANGELOG.md
.changelog-pending/2026-07-21T17-10-16-341b7f0f1ea67e05b14ab5014622e1f93182cdff.md	Pending changelog entry for #695 deleted after being merged into CHANGELOG.md

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Merged PRs: #690, #692, #694, #695] --> B[.changelog-pending/*.md files created]
    B --> C[Release Please bot triggers]
    C --> D[Reads commit metadata for breaking changes / features]
    C --> E[Reads .changelog-pending/*.md files]
    D --> F[PR Description: includes ⚠ BREAKING CHANGES section]
    E --> G[CHANGELOG.md: merges pending entries under Documentation]
    F -.->|Missing in file| G
    G --> H[.changelog-pending/*.md files deleted]
    H --> I[pyproject.toml / uv.lock / manifest: 9.1.0 → 10.0.0]
    I --> J[Release v10.0.0]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Merged PRs: #690, #692, #694, #695] --> B[.changelog-pending/*.md files created]
    B --> C[Release Please bot triggers]
    C --> D[Reads commit metadata for breaking changes / features]
    C --> E[Reads .changelog-pending/*.md files]
    D --> F[PR Description: includes ⚠ BREAKING CHANGES section]
    E --> G[CHANGELOG.md: merges pending entries under Documentation]
    F -.->|Missing in file| G
    G --> H[.changelog-pending/*.md files deleted]
    H --> I[pyproject.toml / uv.lock / manifest: 9.1.0 → 10.0.0]
    I --> J[Release v10.0.0]

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
CHANGELOG.md:3-12
**Breaking changes section absent from CHANGELOG.md**

This major version release bumps from 9.1.0 → 10.0.0 with 9 breaking API changes (symbol removal, parameter type changes across `ApiKeys`, `Authorization`, `Connect`, `Groups`, `Organizations`, `Pipes`, `UserManagement`, `Vault`, and `Widgets`), yet `CHANGELOG.md` contains no `### ⚠ BREAKING CHANGES` section. The Release Please PR description correctly lists all 9 breaking changes, but the file written to disk only has `### Features` and `### Documentation`. Users who inspect `CHANGELOG.md` directly when planning an upgrade will see no indication that the API surface has changed, which increases the risk of silent breakage after upgrading.

_{Reviews (4): Last reviewed commit: "chore: inline release notes from .change..." | Re-trigger Greptile}

[greptile-apps]

Breaking changes section absent from CHANGELOG.md

This major version release bumps from 9.1.0 → 10.0.0 with 9 breaking API changes (symbol removal, parameter type changes across ApiKeys, Authorization, Connect, Groups, Organizations, Pipes, UserManagement, Vault, and Widgets), yet CHANGELOG.md contains no ### ⚠ BREAKING CHANGES section. The Release Please PR description correctly lists all 9 breaking changes, but the file written to disk only has ### Features and ### Documentation. Users who inspect CHANGELOG.md directly when planning an upgrade will see no indication that the API surface has changed, which increases the risk of silent breakage after upgrading.

Prompt To Fix With AI

This is a comment left during a code review.
Path: CHANGELOG.md
Line: 3-12

Comment:
**Breaking changes section absent from CHANGELOG.md**

This major version release bumps from 9.1.0 → 10.0.0 with 9 breaking API changes (symbol removal, parameter type changes across `ApiKeys`, `Authorization`, `Connect`, `Groups`, `Organizations`, `Pipes`, `UserManagement`, `Vault`, and `Widgets`), yet `CHANGELOG.md` contains no `### ⚠ BREAKING CHANGES` section. The Release Please PR description correctly lists all 9 breaking changes, but the file written to disk only has `### Features` and `### Documentation`. Users who inspect `CHANGELOG.md` directly when planning an upgrade will see no indication that the API surface has changed, which increases the risk of silent breakage after upgrading.

How can I resolve this? If you propose a fix, please make it concise.