Skip to content

[release] Minor fixes to release annotation and wheel upload#33129

Merged
simon-mo merged 9 commits intomainfrom
khluu/release_script_fix
Jan 29, 2026
Merged

[release] Minor fixes to release annotation and wheel upload#33129
simon-mo merged 9 commits intomainfrom
khluu/release_script_fix

Conversation

@khluu
Copy link
Copy Markdown
Collaborator

@khluu khluu commented Jan 27, 2026

  • Add commands for CUDA 13.0 Docker images
  • Use twine upload <args> instead of twine <args> upload. The latter caused errors.
  • Use vllm-openai-rocm repo instead of vllm-openai:rocm tag
  • Remove github release part from wheel upload script. This is currently done manually, and if need to be automated, we should separate it into a separate job/script.
  • Rename release wheel script to be PyPI only.

p
Signed-off-by: khluu <khluu000@gmail.com>
@khluu khluu requested a review from simon-mo January 27, 2026 01:35
@mergify mergify bot added the ci/build label Jan 27, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces several fixes and improvements to the release process scripts. It updates the release annotation script to include commands for CUDA 13.0 and CPU wheels, and corrects the Docker repository for ROCm images. The wheel upload script is streamlined to focus solely on PyPI, removing the GitHub release logic and correcting the twine command usage. While these changes are beneficial, I've identified two critical copy-paste errors in the annotate-release.sh script that could result in publishing incorrect Docker images during a release. Please address these issues.

docker tag public.ecr.aws/q9t5s3a7/vllm-release-repo:${BUILDKITE_COMMIT}-x86_64-cu130 vllm/vllm-openai:x86_64-cu130
docker tag vllm/vllm-openai:x86_64-cu130 vllm/vllm-openai:latest-x86_64-cu130
docker tag vllm/vllm-openai:x86_64-cu130 vllm/vllm-openai:v${RELEASE_VERSION}-x86_64-cu130
docker push vllm/vllm-openai:latest-x86_64
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

There seems to be a copy-paste error here. You are pushing vllm/vllm-openai:latest-x86_64, which corresponds to the non-cu130 image. In this block for cu130 images, you should be pushing the latest-x86_64-cu130 tag.

Suggested change
docker push vllm/vllm-openai:latest-x86_64
docker push vllm/vllm-openai:latest-x86_64-cu130

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

Comment @cursor review or bugbot run to trigger another review on this PR

docker tag public.ecr.aws/q9t5s3a7/vllm-release-repo:${BUILDKITE_COMMIT}-x86_64-cu130 vllm/vllm-openai:x86_64-cu130
docker tag vllm/vllm-openai:x86_64-cu130 vllm/vllm-openai:latest-x86_64-cu130
docker tag vllm/vllm-openai:x86_64-cu130 vllm/vllm-openai:v${RELEASE_VERSION}-x86_64-cu130
docker push vllm/vllm-openai:latest-x86_64
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong Docker tag pushed for CUDA 13.0 x86_64 image

High Severity

The docker push command on line 49 pushes vllm/vllm-openai:latest-x86_64 instead of vllm/vllm-openai:latest-x86_64-cu130. This is in the CUDA 13.0 x86_64 section where the preceding lines correctly tag and prepare latest-x86_64-cu130, but then the push command incorrectly references the non-cu130 tag. Following these release instructions would fail to push the correct cu130 latest image.

Fix in Cursor Fix in Web

docker push vllm/vllm-openai:latest-rocm
docker push vllm/vllm-openai:v${RELEASE_VERSION}-rocm
docker tag public.ecr.aws/q9t5s3a7/vllm-release-repo:${BUILDKITE_COMMIT}-aarch64-cu130 vllm/vllm-openai:aarch64-cu130
docker tag vllm/vllm-openai:aarch64 vllm/vllm-openai:latest-aarch64
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong Docker tag command for CUDA 13.0 aarch64 image

High Severity

The docker tag command on line 59 uses vllm/vllm-openai:aarch64 as source and vllm/vllm-openai:latest-aarch64 as destination, but this is in the CUDA 13.0 aarch64 section. Both should include the -cu130 suffix: source should be aarch64-cu130 and destination should be latest-aarch64-cu130. This would result in tagging the wrong image and the subsequent push of latest-aarch64-cu130 would push the wrong content.

Fix in Cursor Fix in Web

p
Signed-off-by: khluu <khluu000@gmail.com>
@DarkLight1337 DarkLight1337 requested a review from tjtanaa January 27, 2026 03:02
docker tag public.ecr.aws/q9t5s3a7/vllm-release-repo:${BUILDKITE_COMMIT}-rocm vllm/vllm-openai-rocm:${BUILDKITE_COMMIT}-rocm
docker tag vllm/vllm-openai-rocm:${BUILDKITE_COMMIT}-rocm vllm/vllm-openai-rocm:latest-rocm
docker tag vllm/vllm-openai-rocm:${BUILDKITE_COMMIT}-rocm vllm/vllm-openai-rocm:v${RELEASE_VERSION}-rocm
docker push vllm/vllm-openai-rocm:latest-rocm
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating this. I will move this to another annotate-rocm-release in my upcoming PR, so that all ROCm docker and whls info are annotated together.

docker tag public.ecr.aws/q9t5s3a7/vllm-release-repo:${BUILDKITE_COMMIT}-rocm vllm/vllm-openai-rocm:${BUILDKITE_COMMIT}-rocm
docker tag vllm/vllm-openai-rocm:${BUILDKITE_COMMIT}-rocm vllm/vllm-openai-rocm:latest-rocm
docker tag vllm/vllm-openai-rocm:${BUILDKITE_COMMIT}-rocm vllm/vllm-openai-rocm:v${RELEASE_VERSION}-rocm
docker push vllm/vllm-openai-rocm:latest-rocm
Copy link
Copy Markdown
Collaborator

@tjtanaa tjtanaa Jan 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khluu since we are using a separate repo, the tag should be latest instead of latest-rocm

docker tag public.ecr.aws/q9t5s3a7/vllm-release-repo:${BUILDKITE_COMMIT}-rocm vllm/vllm-openai-rocm:${BUILDKITE_COMMIT}
docker tag vllm/vllm-openai-rocm:${BUILDKITE_COMMIT} vllm/vllm-openai-rocm:latest
docker tag vllm/vllm-openai-rocm:${BUILDKITE_COMMIT} vllm/vllm-openai-rocm:v${RELEASE_VERSION}
docker push vllm/vllm-openai-rocm:latest
docker push vllm/vllm-openai-rocm:v${RELEASE_VERSION}

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed! thanks for the review

p
Signed-off-by: khluu <khluu000@gmail.com>
@khluu khluu requested a review from Harry-Chen January 27, 2026 07:06
@khluu
Copy link
Copy Markdown
Collaborator Author

khluu commented Jan 27, 2026

Goal is to automate all of the docker push commands... We probably need a different tier of machine only for release though. I'm still paranoid about putting too much permission on postmerge machines.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just remove this file?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh I thought it would be shown here as a file name change, but I guess it's this way because there are diff changes

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

p
Signed-off-by: khluu <khluu000@gmail.com>
@@ -1,108 +0,0 @@
#!/usr/bin/env bash

set -ex
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khluu Is the logic for uploading nightly wheels implemented in some other files?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved! I realized I deleted the wrong file :( they are named very similar

@mergify
Copy link
Copy Markdown

mergify bot commented Jan 29, 2026

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @khluu.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label Jan 29, 2026
@khluu khluu added this to the v0.15.1 Hotfix milestone Jan 29, 2026
khluu added 4 commits January 29, 2026 11:53
p
Signed-off-by: khluu <khluu000@gmail.com>
Signed-off-by: khluu <khluu000@gmail.com>
p
Signed-off-by: khluu <khluu000@gmail.com>
p
Signed-off-by: khluu <khluu000@gmail.com>
@khluu khluu added ready ONLY add when PR is ready to merge/full CI is needed and removed needs-rebase labels Jan 29, 2026
@simon-mo simon-mo merged commit 2284461 into main Jan 29, 2026
11 of 14 checks passed
@simon-mo simon-mo deleted the khluu/release_script_fix branch January 29, 2026 20:09
apd10 pushed a commit to apd10/vllm that referenced this pull request Jan 31, 2026
khluu added a commit that referenced this pull request Feb 2, 2026
Signed-off-by: khluu <khluu000@gmail.com>
(cherry picked from commit 2284461)
PiratePai pushed a commit to PiratePai/epd_shm that referenced this pull request Feb 3, 2026
…oject#33129)

Signed-off-by: khluu <khluu000@gmail.com>
Signed-off-by: Pai <416932041@qq.com>
ItzDEXX pushed a commit to ItzDEXX/vllm that referenced this pull request Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci/build ready ONLY add when PR is ready to merge/full CI is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants