feat(generated): regenerate from spec (8 changes)#495
Conversation
…dd name field to user models
…ization to groups
Greptile SummaryAuto-generated SDK update regenerated from the WorkOS OpenAPI spec, bundling 8 spec changes into a single release. All breaking changes are explicitly flagged in the PR description and a pending changelog entry.
Confidence Score: 5/5Safe to merge — all breaking changes are deliberately spec-driven, fully reflected in the changelog, and the refactoring (ObjectModel → VaultObject, removal of DsyncDeactivated, removal of return_to) has no dangling references left in the codebase. The changes are auto-generated from a versioned OpenAPI spec, every model has a corresponding round-trip test, and the inflection table and RBI type stubs are kept in sync. The only known gap (the compact-drops-nil behaviour on expires_at in create_api_key_expire) was already raised and discussed in a prior review comment. No files require special attention beyond the previously discussed expires_at/compact behaviour in lib/workos/api_keys.rb. Important Files Changed
|
| def create_api_key_expire( | ||
| id:, | ||
| expires_at: nil, | ||
| request_options: {} | ||
| ) | ||
| body = { |
There was a problem hiding this comment.
nil expires_at silently omitted — "clear scheduled expiration" use-case is unreachable
The docstring says "Use null to clear a scheduled future expiration", but the body is built with .compact, which drops any nil value. Calling create_api_key_expire(id: "key_id", expires_at: nil) (the explicit-null form) produces body = {}, identical to omitting the parameter entirely. If the API distinguishes {"expires_at": null} (cancel pending expiry) from an empty body (expire immediately), that distinction is permanently lost here and the "clear scheduled expiration" path can never be exercised.
Summary
feat(api_keys): Add API key expiration and update event support
create_api_key_expireoperation to expire API keys viaPOST /api_keys/{id}/expireApiKeyUpdatedevent class withApiKeyUpdatedDataand related nested models for tracking API key update eventsexpires_atrequired field toApiKeyCreatedDataandApiKeyRevokedDatafeat(user_management)!: Remove return_to param from revoke_session; add name field to user models
return_toparameter fromrevoke_sessionmethod (breaking change)namefield toUser,CreateUser,UpdateUser, andEmailChangeConfirmationUsermodels.rbitype stubs to reflect signature changesfeat(directory_sync): Remove DsyncDeactivated models; add DsyncToken events
DsyncDeactivated,DsyncDeactivatedData, and related enum classes (breaking change)DsyncTokenCreated,DsyncTokenCreatedData,DsyncTokenRevoked, andDsyncTokenRevokedDataevent modelsfeat(vault): Rename ObjectModel class to VaultObject
ObjectModelclass toVaultObjectfor consistency with vault service naming (breaking change)get_nameandget_kvmethods to returnVaultObjectinstead ofObjectModelobjectinflection mapping that no longer appliesfeat(connect): Add name field to UserObject
namefield toUserObjectmodel for Connect applicationsfeat(groups): Move UserOrganizationMembershipBaseListData from authorization to groups
UserOrganizationMembershipBaseListDatamodel from authorization service to groups service (organizational change)feat(types): Add SNOWFLAKE log stream type; remove DOMAIN_SIGN_UP_RATE_LIMIT enum
SNOWFLAKEvalue toAuditLogConfigurationLogStreamTypeenumDOMAIN_SIGN_UP_RATE_LIMITvalue fromRadarStandaloneResponseControlenum (breaking at type level)API_KEY_UPDATEDevent type to webhook endpoint event enumsfeat(user_management)!: Add UserApiKeyUpdatedDataOwner model
UserApiKeyUpdatedDataOwnermodel for API key update events owned by usersTriggered by workos/openapi-spec@dee95fc
BEGIN_COMMIT_OVERRIDE
feat(generated): regenerate from spec (8 changes)
END_COMMIT_OVERRIDE