chore(main): release 8.0.1

[workos-sdk-automation]

🤖 I have created a release beep boop

8.0.1 (2026-05-12)

Bug Fixes

• harden session sealing, log redaction, and webhook tolerance checks (#482) (347fe1e)

---

This PR was generated with Release Please. See documentation.

[workos-sdk-automation]

🤖 Created releases:

• v8.0.1

🌻

[greptile-apps]

Greptile Summary

Automated release PR generated by Release Please, bumping the gem version from 8.0.0 to 8.0.1 to ship the hardening bug fixes merged in #482 (session sealing, log redaction, and webhook tolerance).

• lib/workos/version.rb, Gemfile.lock, and .release-please-manifest.json are each updated consistently to 8.0.1.
• CHANGELOG.md receives a new entry linking back to the bug-fix commit 347fe1e.

Confidence Score: 5/5

All four files are purely version-bump bookkeeping with no logic changes; safe to merge.

Every changed line is a mechanical version string update (8.0.0 → 8.0.1) across the manifest, lock file, version constant, and changelog. There is nothing here that could introduce a regression or break behavior.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 8.0.0 to 8.0.1; no issues.
CHANGELOG.md	8.0.1 release entry added referencing the hardening bug-fix PR #482; no issues.
Gemfile.lock	workos gem version in lock file updated from 8.0.0 to 8.0.1; consistent with version.rb.
lib/workos/version.rb	VERSION constant bumped from "8.0.0" to "8.0.1"; no issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] -->|generates| B[chore: release 8.0.1 PR]
    B --> C[lib/workos/version.rb\nVERSION = 8.0.1]
    B --> D[Gemfile.lock\nworkos 8.0.1]
    B --> E[.release-please-manifest.json\n. = 8.0.1]
    B --> F[CHANGELOG.md\nentry for 8.0.1]
    G[#482 bug-fix PR\nharden session/log/webhook] -->|triggers release| A

Loading

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