Joao Moura 9f097e17e8 test(flow): make the checkpoint-restore guard actually guard ...

The test asserted that flow:resumed was absent from feature usage, but that
signal moved onto the Flow Execution span. The assertion could no longer fail,
so a regression that mis-tagged checkpoint restores as resumes would have gone
unnoticed.

Now asserts the resumed attribute, and waits for the handlers: the manual emit
dispatches asynchronously, so the previous shape also read its result before the
listener had run.

Confirmed it discriminates - keying resumed off _is_execution_resuming again
fails it with [('RestoredFlow', True)] == [('RestoredFlow', False)].

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ASfWmW3RGy4qAQm6s8U9jH

2026-08-11 17:05:12 -07:00

..

cli

Standardize CLI flags to kebab-case (#6880)

2026-08-11 22:17:24 +05:30

crewai

test(flow): make the checkpoint-restore guard actually guard

2026-08-11 17:05:12 -07:00

crewai-core

fix(core): scope span export to our own tracer provider (#6954)

2026-08-11 00:16:27 +00:00

crewai-files

feat: bump versions to 1.15.14 (#6876)

2026-08-08 19:55:33 -03:00

crewai-tools

fix(deps): bump gitpython to 3.1.58 in crewai-tools[github] (#6885)

2026-08-09 13:25:26 -07:00

devtools

feat: bump versions to 1.15.14 (#6876)

2026-08-08 19:55:33 -03:00