chore(main): release 6.0.2

[workos-sdk-automation]

🤖 I have created a release beep boop

6.0.2 (2026-04-14)

Bug Fixes

• slight rename (2b2e9e2)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

Automated release PR bumping the package version from 6.0.1 to 6.0.2, generated by Release Please. The only substantive change shipped in this version is a "slight rename" bug fix (commit 2b2e9e2).

Confidence Score: 5/5

• This PR is safe to merge — it is a fully automated release bump with no logic changes.
• All three changed files are release metadata (manifest, changelog, pyproject.toml). The changes are consistent: every version reference moves from 6.0.1 to 6.0.2. No code, tests, or configuration was modified.
• No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 6.0.1 to 6.0.2 by Release Please automation.
CHANGELOG.md	New 6.0.2 entry added with bug fix reference to commit 2b2e9e2 ("slight rename").
pyproject.toml	Package version updated from 6.0.1 to 6.0.2; no other changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Bug fix commit merged\n'slight rename' - 2b2e9e2] --> B[Release Please detects\nfix: commit]
    B --> C[Release PR generated\nv6.0.1 → v6.0.2]
    C --> D{Files updated}
    D --> E[.release-please-manifest.json\n6.0.1 → 6.0.2]
    D --> F[pyproject.toml\nversion 6.0.1 → 6.0.2]
    D --> G[CHANGELOG.md\nNew 6.0.2 entry added]
    E & F & G --> H[Merge & tag v6.0.2]
    H --> I[Publish to PyPI]

Loading

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

[workos-sdk-automation]

🤖 Created releases:

• v6.0.2
  🌻