chore(main): release 0.8.0

[workos-sdk-automation]

🤖 I have created a release beep boop

0.8.0 (2026-05-01)

Features

• callback: centralize logging and add errorRedirectUrl option (dcc9788)

Bug Fixes

• eliminate server-side bundle leak via lazy handler bodies (#75) (df41d22)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

Automated release PR generated by Release Please, bumping the package version from 0.7.0 to 0.7.1. The only changes are the version field in package.json, the corresponding entry in .release-please-manifest.json, and a new CHANGELOG.md section documenting the server-side bundle leak fix landed in #75.

Confidence Score: 5/5

Safe to merge — purely a version bump and changelog update with no logic changes.

All three changed files are release metadata only (manifest, changelog, package version). No code logic, no security implications, and versions are consistent across all files.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 0.7.0 to 0.7.1 — consistent with package.json and CHANGELOG.md
CHANGELOG.md	New 0.7.1 entry added documenting the server-side bundle leak fix from #75
package.json	Version field bumped from 0.7.0 to 0.7.1 — no other changes

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] -->|generates release PR| B[PR #77]
    B --> C[.release-please-manifest.json\n0.7.0 → 0.7.1]
    B --> D[package.json\nversion 0.7.0 → 0.7.1]
    B --> E[CHANGELOG.md\nadd 0.7.1 entry]
    C & D & E --> F[Merge → publish v0.7.1 to npm]

Loading

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

[workos-sdk-automation]

🤖 Created releases:

• v0.8.0

🌻