chore(main): release 9.1.0

[github-actions]

🤖 I have created a release beep boop

9.1.0 (2026-04-21)

Features

• add support for role_slug in invitation schema (#1567) (ba29409)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This is an automated Release Please PR bumping the package version from 9.0.0 to 9.1.0. The only substantive change included is the addition of role_slug support in the invitation schema (landed in the preceding commit), reflected here via CHANGELOG.md, package.json, .release-please-manifest.json, and package-lock.json updates.

Confidence Score: 5/5

Safe to merge — purely automated version-bump and changelog files with no logic changes.

All four changed files are generated artifacts (manifest, changelog, package metadata, lockfile). No code logic, security-sensitive paths, or custom rule violations were found.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version updated from 9.0.0 to 9.1.0 to match the new release.
CHANGELOG.md	Added 9.1.0 changelog entry documenting the role_slug feature addition; all links and commit hashes look correct.
package.json	Package version bumped to 9.1.0; no other changes.
package-lock.json	Lock file regenerated to reflect the new 9.1.0 version; no dependency changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Release Please Bot"] -->|"Detects merged feature PR #1567\n(role_slug in invitation schema)"| B["Bump version\n9.0.0 → 9.1.0"]
    B --> C["Update .release-please-manifest.json"]
    B --> D["Update package.json"]
    B --> E["Regenerate package-lock.json"]
    B --> F["Append CHANGELOG.md entry"]
    C & D & E & F --> G["PR #1568 — chore(main): release 9.1.0"]
    G -->|"Merge"| H["npm publish @workos-inc/node@9.1.0"]

Loading

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