chore(main): release 9.1.0

[workos-sdk-automation]

🤖 I have created a release beep boop

9.1.0 (2026-06-17)

Bug Fixes

• renovate: explicitly enable minor and patch updates (#493) (c6da3f3)
• Use Thread.current[] instead of Fiber[] for connection cache (#499) (a44d650)

• #495 feat(generated): regenerate from spec (8 changes)

  Features

  • api_keys:
    • Added model ExpireApiKey
    • Added model ApiKeyUpdated
    • Added model ApiKeyUpdatedData
    • Added model ApiKeyUpdatedDataOwner
    • Added model UserApiKeyUpdatedDataOwner
    • Added model ApiKeyUpdatedDataPreviousAttribute
    • Added endpoint POST /api_keys/{id}/expire
  • audit_logs:
    • Added Snowflake to AuditLogConfigurationLogStreamType
  • connect:
    • Added name to UserObject
  • directory_sync:
    • Added model DsyncTokenCreated
    • Added model DsyncTokenCreatedData
    • Added model DsyncTokenRevoked
    • Added model DsyncTokenRevokedData
  • user_management:
    • Added name to user management models
  • webhooks:
    • Added api_key.updated to CreateWebhookEndpointEvents
    • Added api_key.updated to UpdateWebhookEndpointEvents

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This is an automated Release Please PR that bumps the gem version from 9.0.0 to 9.1.0, updates Gemfile.lock, adds a CHANGELOG.md entry, and deletes the consumed pending-changelog file. There is a notable discrepancy between the PR title/description (which declares a 10.0.0 major release with breaking changes) and the actual files changed (which consistently set the version to 9.1.0).

• lib/workos/version.rb, .release-please-manifest.json, and Gemfile.lock are all updated to 9.1.0.
• The CHANGELOG.md entry for 9.1.0 mixes Release Please's standard format with the raw pending-changelog format, producing an inconsistent section compared to prior entries.
• The deleted pending changelog file listed multiple breaking changes (removal of return_to from RevokeSession, removal of DsyncDeactivated* models, etc.) that do not appear in the 9.1.0 CHANGELOG entry and have not been accounted for with a major version bump.

Confidence Score: 4/5

The version bump is internally consistent across all files, but the declared release version in the PR title and description does not match what was actually committed.

All version-related files agree on 9.1.0, so there is no internal inconsistency in the gem itself. However, the PR description documents breaking changes that would require a major version bump under semver. If those breaking changes are truly included in the code shipped by the referenced PRs, consumers who pin to ~> 9.0 would receive API-incompatible changes silently.

lib/workos/version.rb and .release-please-manifest.json — verify whether the version should be 10.0.0 given the breaking changes described in the PR.

Important Files Changed

Filename	Overview
lib/workos/version.rb	Version bumped from 9.0.0 to 9.1.0, but PR title and description declare a 10.0.0 major release with breaking changes
.release-please-manifest.json	Manifest updated to 9.1.0 — inconsistent with PR title claiming 10.0.0
CHANGELOG.md	New 9.1.0 entry added; mixes Release Please bullet format with raw pending-entry list format; breaking changes from the pending file are absent
Gemfile.lock	Lock file correctly reflects the 9.1.0 version bump in both PATH and CHECKSUMS sections
.changelog-pending/2026-06-03T19-21-00-dee95fc33c4f813ac60adfa8c57d210db8183dd8.md	Pending changelog entry deleted as part of the release process — expected

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot triggers] --> B{Determine version bump}
    B -->|PR title/desc says breaking changes| C[Expected: 10.0.0 major bump]
    B -->|Actual files changed| D[Actual: 9.1.0 minor bump]
    C -.->|Mismatch| D
    D --> E[lib/workos/version.rb → 9.1.0]
    D --> F[.release-please-manifest.json → 9.1.0]
    D --> G[Gemfile.lock → 9.1.0]
    D --> H[CHANGELOG.md → 9.1.0 entry added]
    H --> I[Bug Fixes section - Release Please format]
    H --> J[Features section - raw pending format mixed in]
    K[.changelog-pending/*.md] -->|Deleted| L[Consumed by release]

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[Release Please Bot triggers] --> B{Determine version bump}
    B -->|PR title/desc says breaking changes| C[Expected: 10.0.0 major bump]
    B -->|Actual files changed| D[Actual: 9.1.0 minor bump]
    C -.->|Mismatch| D
    D --> E[lib/workos/version.rb → 9.1.0]
    D --> F[.release-please-manifest.json → 9.1.0]
    D --> G[Gemfile.lock → 9.1.0]
    D --> H[CHANGELOG.md → 9.1.0 entry added]
    H --> I[Bug Fixes section - Release Please format]
    H --> J[Features section - raw pending format mixed in]
    K[.changelog-pending/*.md] -->|Deleted| L[Consumed by release]

Loading

_{Reviews (5): Last reviewed commit: "chore: correct release version to 9.1.0" | Re-trigger Greptile}

[greptile-apps]

Version mismatch between PR metadata and actual release

The PR title says "release 10.0.0" and the PR description explicitly documents this as ## [10.0.0] with ⚠ BREAKING CHANGES (removal of return_to from revoke_session, addition of UserApiKeyUpdatedDataOwner as a new required model). However, the actual version set in lib/workos/version.rb, .release-please-manifest.json, Gemfile.lock, and CHANGELOG.md is 9.1.0 — a minor (non-breaking) bump. Semver requires a major version increment when public API compatibility is broken, so either the version should be 10.0.0 to match the declared breaking changes, or the PR description is stale and the breaking changes were intentionally excluded from this release.