Skip to content

chore(automation-client, event-catalog-client): Event Catalog trigger support - #481

Closed
karlrank wants to merge 1 commit into
mainfrom
feat/event-catalog-trigger
Closed

chore(automation-client, event-catalog-client): Event Catalog trigger support#481
karlrank wants to merge 1 commit into
mainfrom
feat/event-catalog-trigger

Conversation

@karlrank

@karlrank karlrank commented Sep 3, 2026

Copy link
Copy Markdown
Member

What

Regenerated clients for the Event Catalog → automation trigger feature.

  • @epilot/automation-client (minor → 2.37.0): EventCatalogTrigger, TriggerEventEventCatalog, TriggerEventPayloadRef, ConditionStatement.source.originType: event, searchFlows trigger_event_name. Also picks up the already-merged but unreleased graph_context schemas.
  • @epilot/event-catalog-client (patch → 0.6.4): _automation_chain on TriggerEventPayload and Event.

Changesets included. Both clients build. Source specs: automation-api feat/event-catalog-trigger, event-catalog-api feat/automation-chain-passthrough — release after those APIs are deployed.

Related MRs (Event Catalog → automation trigger)

Deploy order: svc-webhooks → event-catalog-api → publish automation-shared 2.5.0 → automation-workers → automation-api → root-config translations → UIs; release the SDK clients afterwards.

… support

automation-client: EventCatalogTrigger, TriggerEventEventCatalog,
TriggerEventPayloadRef, ConditionStatement originType 'event',
searchFlows trigger_event_name (minor).
event-catalog-client: _automation_chain on TriggerEventPayload and Event (patch).
@karlrank karlrank closed this Sep 3, 2026
@karlrank
karlrank deleted the feat/event-catalog-trigger branch September 3, 2026 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant