Skip to content

fix(events): rename error event data key from message to text#63

Merged
galuszkm merged 1 commit into
mainfrom
fix/mg/normalize-error-event
Jun 22, 2026
Merged

fix(events): rename error event data key from message to text#63
galuszkm merged 1 commit into
mainfrom
fix/mg/normalize-error-event

Conversation

@galuszkm

Copy link
Copy Markdown
Member

Description

The ERROR event emitted by EventPublisher used data["message"] as the key for the exception string, while every other event that carries a human-readable string payload uses data["text"] (TOKEN, REASONING, AGENT_COMPLETE). Renames the key to text for consistency.

Related Issues

N/A

Type of Change

  • Breaking change

YAML / API Impact

No schema or Python API changes. Breaking only for consumers reading event.data["message"] on ERROR events — they must switch to event.data["text"]. All other event shapes are unchanged.

Testing

  • I ran uv run just check (lint + type check)
  • I ran uv run just test for overall testing
  • I added or updated tests that prove my fix is effective or my feature works
  • I verified existing examples in examples/ still work

Checklist

  • I have read the CONTRIBUTING document
  • I have updated the documentation accordingly
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

Note: Downstream consumers (e.g. strands-compose-agentcore) that read error.data["message"] need to be updated to error.data["text"].

Normalizes the ERROR event schema — all events that carry a human-readable
string payload now use the `text` key consistently.
@galuszkm galuszkm merged commit 70ea14a into main Jun 22, 2026
14 of 15 checks passed
@galuszkm galuszkm deleted the fix/mg/normalize-error-event branch June 22, 2026 21:25
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