[CI] Move DockerHub and PyPI publish steps to end of release pipeline

[khluu]

Summary

• Moved the "Publish release images to DockerHub" block + step and the "Publish wheels to PyPI" group to the very end of the release pipeline
• All build steps (including ROCm) now complete before the final publish actions
• No changes to dependencies or step logic — only positional reordering

Test plan

• Verify the Buildkite pipeline YAML parses correctly
• Confirm depends_on references still resolve to the correct step IDs
• Trigger a dry-run release build to validate step ordering

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[gemini-code-assist]

Code Review

This pull request moves the DockerHub and PyPI publishing steps to the end of the Buildkite release pipeline to ensure all builds are finished before publishing. A review comment suggests adding a condition to the Publish wheels group to prevent manual confirmation blocks from appearing during nightly builds.

[gemini-code-assist]

The Publish wheels group is missing the if: build.env("NIGHTLY") != "1" condition. While this inconsistency existed in the original position, moving these steps to the end of the pipeline is a good opportunity to ensure that release-specific manual blocks do not appear during automated nightly builds. Adding this condition will prevent the PyPI confirmation block from showing up in nightly pipelines.

  - group: "Publish wheels"
    if: build.env("NIGHTLY") != "1"
    key: "publish-wheels"

[Harry-Chen]

@khluu maybe you want to trigger a dryrun and see if it works?

[khluu]

I created a job here and the 2 jobs got moved to the end of the pipeline https://buildkite.com/vllm/release-v2/builds/1517