chore(main): release 9.5.0

[workos-sdk-automation]

🤖 I have created a release beep boop

9.5.0 (2026-07-06)

Features

• generated: UserManagement, Radar (batch f510ddfb) (#514) (200cafd)

---

This PR was generated with Release Please. See documentation.

[workos-sdk-automation]

🤖 Created releases:

• v9.5.0

🌻

[greptile-apps]

Greptile Summary

This PR prepares the workos Ruby gem for the 9.5.0 release. The main changes are:

• Promotes the pending release notes into CHANGELOG.md.
• Updates the Release Please manifest from 9.4.0 to 9.5.0.
• Updates WorkOS::VERSION and the local lockfile entries to 9.5.0.

Confidence Score: 5/5

The release metadata updates are straightforward and limited to versioning, changelog, and lockfile bookkeeping.

The changed files align with an automated gem release and do not modify runtime behavior beyond the published version constant.

T-Rex Logs

What T-Rex did

• Recorded the pre-change state showing WorkOS::VERSION at 9.4.0, a present release-please manifest, and Gemfile.lock at 9.4.0 with a pending changelog file.
• Recorded the post-change state showing WorkOS::VERSION at 9.5.0, the release-please manifest updated, Gemfile.lock at 9.5.0, and the pending changelog file absent, with a 9.5.0 CHANGELOG.md section containing the feat(generated): UserManagement, Radar (batch f510ddfb) #514 user_management notes.
• Reviewed the verification logs to corroborate the before and after observations and support the transitions observed in the state change.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore: update Gemfile.lock" | Re-trigger Greptile}