chore(main): release 0.10.0

[workos-sdk-automation]

🤖 I have created a release beep boop

0.10.0 (2026-06-24)

⚠ BREAKING CHANGES

• requires @workos-inc/node >=10.4.0 and Node >=22.11.

Bug Fixes

• require @workos-inc/node >=10.4.0 (eventemitter3 Vite dev crash #106) (#107) (424a712)
• scope getOrganization lookup to the authenticated session (#108) (61716ef)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This PR prepares the 0.10.0 release. The main changes are:

• Bumps the package version to 0.10.0.
• Updates the release-please manifest to 0.10.0.
• Adds the 0.10.0 changelog entry with breaking-change and bug-fix notes.

Confidence Score: 5/5

Safe to merge: the changes are limited to release metadata and changelog updates.

The touched files only update versioning and release notes for an automated release, with no runtime code changes.

T-Rex Logs

What T-Rex did

• Updated the release metadata from 0.9.1 to 0.10.0 by bumping package.json version, updating the manifest root value, and marking 0.10.0 as the first release heading in the CHANGELOG.

_{Ran code and verified through T-Rex}

_{Reviews (2): Last reviewed commit: "chore(main): release 0.10.0" | Re-trigger Greptile}

[greptile-apps]

Align Node minimum The release notes tell consumers that Node >=22.11 is supported, but the locked Vite/tooling dependency set requires ^20.19.0 || >=22.12.0 in many packages. A consumer who upgrades based on this breaking-change note and selects Node 22.11.x can satisfy this package guidance while still hitting dependency engine failures during install or build. Please update the documented minimum to match the actual supported toolchain range.

Artifacts

Repro: generated Node engine metadata verification script

• Contains supporting evidence from the run (text/javascript; charset=utf-8).

Repro: verbose verifier output showing CHANGELOG >=22.11 and dependency engine rejection of Node 22.11.0

• Keeps the command output available without making the summary code-heavy.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review.
Path: CHANGELOG.md
Line: 8

Comment:
**Align Node minimum** The release notes tell consumers that Node `>=22.11` is supported, but the locked Vite/tooling dependency set requires `^20.19.0 || >=22.12.0` in many packages. A consumer who upgrades based on this breaking-change note and selects Node `22.11.x` can satisfy this package guidance while still hitting dependency engine failures during install or build. Please update the documented minimum to match the actual supported toolchain range.

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

[workos-sdk-automation]

🤖 Created releases:

• v0.10.0

🌻