Joao Moura 0f14e159cd fix(tracing): a same-millisecond tie keeps the record already there; nothing is recorded inside a deployment ...

- The times in the record are stored to the millisecond; two runs finishing
  in the same millisecond compared equal and the later writer won, which
  could leave the older run recorded. A tie now keeps what is there. No
  finer order is worth a field in the file.
- recording_enabled() is false when the platform's integration token is
  present: a deployment normally never reaches this code (the host binds
  the trace before crewAI would start its own), but a container that did
  not would have written a file the platform never reads, against what the
  docs promise. Test added.

89 passed; ruff and mypy clean.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-20 17:39:21 -07:00

..

cli

feat(tracing): record the last traced run for crewai eval instead of printing it

2026-09-20 00:48:05 -07:00

crewai

fix(tracing): a same-millisecond tie keeps the record already there; nothing is recorded inside a deployment

2026-09-20 17:39:21 -07:00

crewai-core

feat(cli): improve platform integration setup UX (#7453)

2026-09-17 11:35:32 -07:00

crewai-files

feat: bump versions to 1.15.22 (#7520)

2026-09-16 22:04:49 +00:00

crewai-tools

fix(tools): preserve directory listing paths (#7548)

2026-09-17 22:47:38 +05:30

devtools

feat: bump versions to 1.15.22 (#7520)

2026-09-16 22:04:49 +00:00