Joao MouraandClaude Opus 5.5 b26ccaf440 Never run the crew toward an AMP the login must not reach; check before asking ...

`crewai eval` now refuses to run the crew whenever a credential of this
machine would go with the trace to an AMP it does not trust, whatever the
tracing setting: `tracing=True` in code is invisible to the CLI, and a
project's crewai older than the handshake sends the credential wherever
the run traces. The run app's Evaluate makes the same check before it
asks anything, so a yes can never write CREWAI_TRACING_ENABLED=true to
`.env` for a re-run that is then refused.

Which credentials are this machine's is read from the environment as it
was before any project `.env` was loaded (`run_crew.environment_before_project`),
so on Evaluate's re-run a CREWAI_USER_PAT the project's own `.env` brought
is the project's, as on any run of it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-18 23:31:53 -07:00

..

cli

Never run the crew toward an AMP the login must not reach; check before asking

2026-10-18 23:31:53 -07:00

crewai

fix(cli): keep the saved login off a project's AMP on every path crewai eval runs

2026-10-18 23:07:51 -07:00

crewai-core

fix(cli): turn tracing on once with a note, pin the eval handshake, and keep the saved login to trusted AMPs

2026-10-18 23:07:51 -07:00

crewai-files

fix: resolve pip-audit dependency findings (#8221)

2026-10-16 09:14:52 +00:00

crewai-tools

fix: resolve pip-audit dependency findings (#8221)

2026-10-16 09:14:52 +00:00

devtools

feat: bump versions to 1.15.28 (#8146)

2026-10-14 01:42:13 -03:00