Skip to content

chore(main): release 9.0.0#1558

Draft
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main--components--node
Draft

chore(main): release 9.0.0#1558
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main--components--node

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 15, 2026

🤖 I have created a release beep boop

9.0.0 (2026-04-21)

⚠ BREAKING CHANGES

  • rename portal to adminPortal (#1562)
  • standardize authorization list endpoint pagination (#1553)
  • Drop Node.js v20 support, require v22.11+ (#1560)
  • Remove legacy FGA package (#1559)

Features

  • Add groups endpoints and group event types (#1564) (cb0c46d)
  • adding three new conection types to node SDK connection type enums (#1389) (c11cfd6)
  • standardize authorization list endpoint pagination (#1553) (7a91d74)
  • Update Node SDK to include auditlogs.listSchemas (#1457) (c31736d)

Bug Fixes

  • errors: type server/auth errors and restore type compatibility (#1561) (e149152)
  • Export ConflictException and add code (#1563) (a5524f8)
  • Remove extractVersion from matchUpdateTypes rules (#1557) (f6272ea)
  • rename portal to adminPortal (#1562) (80614d4)

Code Refactoring


This PR was generated with Release Please. See documentation.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 15, 2026

Greptile Summary

This is an automated Release Please PR bumping the package from v8.13.0 to v9.0.0. The major version increment is warranted by three breaking changes: standardized authorization list endpoint pagination, dropping Node.js v20 support (now requires >=22.11.0), and removal of the legacy FGA package. Version numbers are consistent across package.json, package-lock.json, and .release-please-manifest.json.

Confidence Score: 5/5

Safe to merge — automated release PR with consistent version bumps and no logic changes.

All four changed files are version/changelog bookkeeping generated by Release Please. Versions are consistent across package.json, package-lock.json, and .release-please-manifest.json. The major bump is justified by the three documented breaking changes. No custom rules are violated.

No files require special attention.

Important Files Changed

Filename Overview
package.json Version bumped from 8.13.0 to 9.0.0; engines.node updated to >=22.11.0; no other changes.
package-lock.json Root package version bumped to 9.0.0; lockfileVersion 3 is unchanged; consistent with package.json.
.release-please-manifest.json Version entry updated to "9.0.0" to track the new release; consistent with package.json.
CHANGELOG.md 9.0.0 release section prepended with all three breaking changes, one feature, one bug fix, and two refactors accurately documented.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] --> B[Bump version: 8.13.0 → 9.0.0]
    B --> C[package.json\nversion: 9.0.0\nengines.node: >=22.11.0]
    B --> D[package-lock.json\nversion: 9.0.0]
    B --> E[.release-please-manifest.json\n.: 9.0.0]
    B --> F[CHANGELOG.md\nv9.0.0 entry prepended]
    C & D & E & F --> G[Major version published\n@workos-inc/node@9.0.0]

    subgraph Breaking Changes
        BC1[⚠ Standardize authorization\nlist endpoint pagination]
        BC2[⚠ Drop Node.js v20\nrequire v22.11+]
        BC3[⚠ Remove legacy\nFGA package]
    end
    BC1 & BC2 & BC3 --> A
Loading

Reviews (4): Last reviewed commit: "chore(main): release 9.0.0" | Re-trigger Greptile

@github-actions github-actions bot changed the title chore(main): release 8.13.1 chore(main): release 9.0.0 Apr 17, 2026
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node branch 3 times, most recently from 311f43c to 2a36ac1 Compare April 17, 2026 20:34
@gjtorikian gjtorikian marked this pull request as draft April 17, 2026 22:07
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node branch 3 times, most recently from 5a2e1d8 to 447ec9e Compare April 20, 2026 13:04
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node branch 4 times, most recently from 92be66f to 9cb53c9 Compare April 21, 2026 16:18
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node branch from 9cb53c9 to 7d5f902 Compare April 21, 2026 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant