chore(main): release 5.2.0

[workos-sdk-automation]

🤖 I have created a release beep boop

5.2.0 (2026-04-27)

Features

• Add script/setup for pre-generation dependency installation (edc2543)
• surface error metadata from API responses (#369) (ece118b)

Bug Fixes

• generated: update generated SDK from spec changes (#372) (0ee912a)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

Automated release PR generated by Release Please, bumping the SDK version from 5.1.0 to 5.2.0. The version string is consistently updated across all three relevant files: .release-please-manifest.json, CHANGELOG.md, and lib/Version.php.

Confidence Score: 5/5

Safe to merge — mechanical version bump with no logic changes.

All three changed files are purely version metadata updates (manifest, changelog, PHP constant). Version strings are consistent across all files and no logic, security, or behavioral changes are introduced.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 5.1.0 to 5.2.0 — straightforward manifest update
CHANGELOG.md	Adds 5.2.0 changelog entry documenting new features and bug fixes
lib/Version.php	SDK_VERSION constant updated from 5.1.0 to 5.2.0, consistent with manifest and changelog

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] --> B[Bump .release-please-manifest.json\n5.1.0 → 5.2.0]
    A --> C[Update CHANGELOG.md\nAdd 5.2.0 entry]
    A --> D[Update lib/Version.php\nSDK_VERSION = '5.2.0']
    B & C & D --> E[Release 5.2.0 Tagged & Published]

Loading

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

[tjmartin69]

Any chance this can be tagged I could really do with this - surface error metadata from API responses so I can upgrade

[workos-sdk-automation]

🤖 Created releases:

• 5.2.0

🌻