Files
crewAI/lib/cli/tests/deploy
João MouraandClaude Opus 5.5 8dcb00584f feat(cli): crewai deploy push --force, and why AMP held a push back (#8150)
* feat(cli): crewai deploy push --force, and why AMP held a push back

AMP now holds back a redeploy while a models comparison is running on the
deployment (crewAIInc/crewai-plus#4776): a redeploy restarts the workers
and the comparison loses its runs (pr_security_reviewer, 2026-10-14). It
answers 409 {"error": "comparison_running", "message": ...}.

- `crewai deploy push --force` goes ahead anyway: deploy_by_uuid /
  deploy_by_name send {"force": true} and update_crew_from_zip a force field
  (crewai-core and the CLI's own copy), only when asked — an unforced push
  sends exactly what it always did, and an older AMP ignores the field.
- A push AMP held back prints AMP's sentence (which names --force) and
  "Nothing was deployed.", and exits 1 — not the bare error code.

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

* test(llms): Claude 3.5 Sonnet v2 on Bedrock has a 200k window in the refreshed catalog

The 1.15.28 release refreshed the packaged LiteLLM catalog, which now lists
anthropic.claude-3-5-sonnet-20241022-v2:0 at 200,000 input tokens (it had
1,000,000), the model's documented window. The test still expected 1M, so
every PR's test job failed on main's own catalog.

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

* fix(cli): AMP's hold-back sentence is printed literally

Review on #8150: the comparison_running message went through Rich markup,
so a bracketed word in it vanished and a stray closing tag raised
MarkupError before "Nothing was deployed." could print. It is printed with
markup=False now; a test sends one with both.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 09:58:28 -03:00
..