Skip to content

chore(main): release 10.4.0 - #551

Open
workos-sdk-automation[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--components--workos
Open

workos-sdk-automation[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--components--workos

Conversation

@workos-sdk-automation

@workos-sdk-automation workos-sdk-automation Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

10.4.0 (2026-09-16)

Features

  • agents: Add parameter AgentsSessions.list.organization_id (#553) (f8fc90e)
  • generated: Pipes (batch 8ad8e447) (#550) (429d26d)
  • pipes: Update Pipes API surface (#553) (f8fc90e)
  • user_management: Add user management API surface (#553) (f8fc90e)

Bug Fixes

  • multi_factor_auth: Change errors for endpoint POST /auth/factors/{id}/challenge (#556) (427e733)
  • pipes: Update Pipes API surface (#553) (f8fc90e)

This PR was generated with Release Please. See documentation.

@greptile-apps

greptile-apps Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 5/5

The release metadata is internally consistent and the PR appears safe to merge.

Summary

This release PR prepares version 10.4.0 by synchronizing the gem version, release manifest, lockfile metadata, and changelog while consuming the corresponding pending changelog entries.

  • Updates WorkOS::VERSION and release metadata from 10.3.0 to 10.4.0.
  • Consolidates pending entries for the generated API changes into CHANGELOG.md.
  • Keeps the gem’s lockfile version aligned with the released package.

Reviews (4) · Last reviewed commit: "chore: update Gemfile.lock"

@workos-sdk-automation
workos-sdk-automation Bot force-pushed the release-please--branches--main--components--workos branch 2 times, most recently from 19e26cf to ef06c76 Compare September 15, 2026 17:06
@workos-sdk-automation
workos-sdk-automation Bot force-pushed the release-please--branches--main--components--workos branch from 68dcd04 to 84ca851 Compare September 16, 2026 19:31
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