[OpenAPI] Spec updates for keycloak-api

[SferaDev]

This is an autogenerated PR to update the OpenAPI spec with the latest merged changes.

Before merging these changes, please review the update and test it out.

[changeset-bot]

🦋 Changeset detected

Latest commit: f3c177b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
keycloak-api

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
openapi-clients	Error			Nov 4, 2025 10:32pm

[vercel]

Suggested change

	on?: void;
	["reset-on"]?: void;
	on?: unknown;
	["reset-on"]?: unknown;

The on and reset-on properties in WorkflowRepresentation are typed as void, which means they cannot hold any meaningful data and can only be undefined.

View Details

Analysis

WorkflowRepresentation properties typed as void prevent workflow configuration

What fails: WorkflowRepresentation.on and WorkflowRepresentation["reset-on"] are typed as void instead of unknown, preventing assignment of workflow event configuration values

How to reproduce:

import { WorkflowRepresentation } from './packages/keycloak-api/src/admin/schemas';

const workflow: WorkflowRepresentation = {
  id: "test",
  on: "some-event", // TypeScript error: Type 'string' is not assignable to type 'void'
  "reset-on": ["event1", "event2"] // TypeScript error: Type 'string[]' is not assignable to type 'void'
};

Result: TypeScript compilation fails with "Type 'string' is not assignable to type 'void'" errors

Expected: Properties should accept any values since the Keycloak OpenAPI spec defines them as {} (empty object/any type), similar to how other event properties like onValues and onEventsReset are properly typed as string[]