Update qwen3.5-fp8-mi325x-sglang SGLang image to v0.5.12-rocm720-mi30x

[Klaud-Cold]

Updates SGLang image for qwen3.5-fp8-mi325x-sglang from v0.5.10-rocm720-mi30x to v0.5.12-rocm720-mi30x.
\nRef #1154

Generated with Claude Code

[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]

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.

[claude]

LGTM, straightforward SGLang image version bump.

Extended reasoning...

Overview

This PR bumps the SGLang image for the qwen3.5-fp8-mi325x-sglang benchmark config from v0.5.10-rocm720-mi30x to v0.5.12-rocm720-mi30x in .github/configs/amd-master.yaml, with a matching entry added to perf-changelog.yaml. Two-line change to a single config entry plus the changelog stub.

Security risks

None. The change only modifies a container image tag string used by a benchmark sweep and a YAML changelog entry. No code, auth, crypto, or permissions are touched.

Level of scrutiny

Very low. This is a mechanical version bump following an established pattern used throughout the repo (numerous prior PRs do the equivalent for other configs). The new image tag follows the same naming convention as the previous one and matches the format used by sibling entries.

Other factors

The pr-link: XXX placeholder in perf-changelog.yaml looks like the auto-template's value pre-merge — consistent with how other entries in this PR's automation flow are handled. No bugs were flagged by the bug hunting system and no human reviewer comments are outstanding (only the standard recipe-reminder bot comments).

[github-actions]

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

[github-actions]

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

[functionstackx]

/reuse-sweep-run

[github-actions]

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