Add DeepSeek-V4-Pro as tier 1 model

[juanmichelini]

[juanmichelini]

@OpenHands

[openhands-ai]

I'm on it! juanmichelini can track my progress at all-hands.dev

[openhands-ai]

Summary

I addressed issue #92 "Add DeepSeek-V4-Pro as tier 1 model" by making minimal, focused changes and opening PR #93.

Checklist of requirements

• Reviewed the task — issue title clearly asked for DeepSeek-V4-Pro as tier 1; body/comments had no extra context.
• Added DeepSeek-V4-Pro to the source of truth (MODEL_RELEASE_DATES in scripts/run_all_models.py, date 2026-05-15 as a placeholder, flagged in the PR description).
• Made it tier 1 by adding a narrow ^DeepSeek-V4-Pro$ pattern to TIER_1_PATTERNS in scripts/track_llm_support.py (intentionally narrow so existing DeepSeek-V3.2-Reasoner stays tier 2).
• Added aliases in MODEL_ALIASES (deepseek-v4-pro, deepseek/deepseek-v4-pro).
• Added tests to tests/test_track_llm_support.py: one for tier classification, one for aliases, one for the release date.
• Ran tests — python -m pytest tests/test_track_llm_support.py -q → 92 passed.
• Branch named with openhands/ prefix (openhands/issue-92-deepseek-v4-pro).
• Committed and pushed with a clear message and Co-authored-by: openhands.
• Opened PR via create_pr tool with description mentioning "Closes Add DeepSeek-V4-Pro as tier 1 model #92" and an AI disclosure note. No PR template exists in the repo, so no template sections to fill in.

Conciseness

The changes are minimal and self-contained: only the three intended files were modified (scripts/run_all_models.py, scripts/track_llm_support.py, tests/test_track_llm_support.py), all changes are directly tied to adding the new model. No extraneous edits, no new files, no leftover scratch files.

Caveats called out in the PR

• Release date 2026-05-15 is a placeholder; reviewer should update if the official date differs.
• SaaS verified-models database entry (Admin API) is intentionally out of scope and noted as a follow-up.