[Klaud Cold] Update minimaxm2.5-fp4-mi355x-vllm vLLM ROCm image to v0.22.0

[functionstackx]

Summary

Update vLLM ROCm image from v0.21.0 to v0.22.0

Recipes touched: minimaxm2.5-fp4-mi355x-vllm

Test plan

• full-sweep-enabled sweep passes.

🤖 Generated with Claude Code

---

Note

Low Risk
Config-only container image pin for a single benchmark recipe; no application code, auth, or sweep matrix changes.

Overview
Bumps the MiniMax-M2.5 MXFP4 MI355X vLLM benchmark recipe (minimaxm2.5-fp4-mi355x-vllm) from vllm/vllm-openai-rocm:v0.21.0 to v0.22.0 in .github/configs/amd-master.yaml. Model, runner, and fixed-seq-len search space are unchanged.

Adds a matching perf-changelog.yaml entry for config-key minimaxm2.5-fp4-mi355x-vllm.

^{Reviewed by Cursor Bugbot for commit 5c4abc6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

• https://docs.sglang.io/cookbook/intro
• https://recipes.vllm.ai/

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

• https://github.com/vllm-project/recipes
• https://github.com/sgl-project/sglang/tree/main/docs_new

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=26696259283
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=26696259283

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=26696260751
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=26696260751

[functionstackx]

/reuse-sweep-run

[github-actions]

see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=26699216321
see unofficial run visualizer at https://inferencex.semianalysis.com/evaluation?unofficialRun=26699216321