Files
crewAI/lib/cli/tests/deploy
João MouraandClaude Opus 5.5 744bf60367 fix(cli): show why a deployment failed and fix deploy remove and lockfile checks (#8083)
* fix(cli): show why a deployment failed and fix deploy remove and lockfile checks

- deploy status prints AMP's error_message and error_suggested_fix when a
  deployment has failed, verbatim (no Rich markup), instead of only
  "Provisioning Failed, try again."
- deploy remove -u names the removed UUID instead of the local project, and
  a failed removal prints the API's error.
- deploy validate asks `uv lock --check` (offline) whether uv.lock is current
  instead of comparing file times, which flagged metadata-only edits that
  `uv lock` never clears. File times remain the fallback without uv or for
  poetry.lock.

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

* docs: note that deploy status prints the failure reason

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

* fix(cli): print deploy validate findings without Rich markup

render_report printed codes, titles, details and hints as Rich markup, so
bracketed text vanished: `[stale_lockfile]`, `[project]`,
`[tool.hatch.build.targets.wheel]`, `crewai[tools]`. Raw `uv` stderr in
the new unverified_lockfile detail could also raise MarkupError on a stray
closing tag. Escape every finding field. Also bound the test fixture's
`uv lock` with a timeout.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 17:21:16 -03:00
..