Release as latest

[ilopezluna]

This pull request removes the separate workflow for promoting Docker images to the latest tag and streamlines the release process by always tagging built images as latest within the main release workflow. The previous option to conditionally push the latest tag using the pushLatest input has been eliminated, and the logic for promoting images is now handled directly in the release workflow.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Hey - I've left some high level feedback:

• The inline shell that builds the Docker tags is now quite repetitive; consider using a small loop over the variants (cpu, cuda, vllm-cuda, etc.) to generate both $RELEASE_TAG and latest tags to reduce duplication and the chance of inconsistencies on future edits.
• Now that every run pushes latest, it may be worth explicitly constraining when the release workflow can be triggered (e.g., only on tagged releases or excluding prerelease tags) so that accidental or prerelease runs don’t overwrite the latest image.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The inline shell that builds the Docker tags is now quite repetitive; consider using a small loop over the variants (cpu, cuda, vllm-cuda, etc.) to generate both `$RELEASE_TAG` and `latest` tags to reduce duplication and the chance of inconsistencies on future edits.
- Now that every run pushes `latest`, it may be worth explicitly constraining when the release workflow can be triggered (e.g., only on tagged releases or excluding prerelease tags) so that accidental or prerelease runs don’t overwrite the `latest` image.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[doringeman]

🤞