Event consumers switch to canonical camelCase JSON keys
Event or EventsFilter JSON fields or the actedUpon query parameterPreviously, consumers still read fields such as event.created_at, event.user_id, event.system_id, and snake_case event-summary keys while meshkit was at v1.0.6. They now read the canonical camelCase fields and summary keys; getEventFilter also accepts the legacy acted_upon query parameter as a fallback.
Show release-note lines
- chore(deps): bump meshkit v1.0.6 -> v1.0.7 + flip Event consumer reads @leecalcote (#18987)github.com/meshery/meshery/releases/tag/v1.0.14