[CI] CI: respect docker login input in release builds

[gyohuangxin]

Summary

• Add an explicit docker_login input to the direct Aiter Release Package manual workflow.
• Stop treating every workflow_dispatch event as an implicit Docker login request.
• Only configure Docker Hub secret names and run Docker login when inputs.docker_login is true.

This fixes release automation manual runs where the caller passes docker_login: false, but the reusable workflow previously converted it back to true because the caller event was workflow_dispatch.

Test plan

• python3 -c "import yaml; yaml.safe_load(open('.github/workflows/aiter-release.yaml')); print('yaml ok')"
• git diff --check

[github-actions]

🏷️ CI Guide

Runs automatically on every PR:

• ✅ Pre-checks (submodule verification, code formatting)
• ✅ Aiter op tests (gfx942 + gfx950)
• ✅ Triton tests on MI35X (only when aiter/ops/triton/** or related paths are changed)

Extended tests (opt-in via labels):

Label	Tests
ci:gfx1250-ffm-triton	Run the five-shard gfx1250 FFM Triton test suite
ci:triton-300x	Run an additional Triton test job on MI300X in PRs; main branch always runs both MI35X and MI300X
multigpu	Aiter multi-GPU tests on the 8-GPU runner
ci:sglang	SGLang integration tests: DeepSeek-R1-MXFP4 accuracy, Qwen 3.5 accuracy
ci:atom	ATOM benchmark: DeepSeek-R1-0528, GPT-OSS-120B
ci:atom_full	ATOM accuracy suite for PR and main models from ATOM models_accuracy.json
ci:vllm	vLLM benchmark: GPT-OSS-120B, DeepSeek-R1-0528, Kimi-K2.5
ci:all	All standard extended tests (excludes ci:atom_full)

Only add ci:atom_full for FlyDSL or Triton upgrades.
Add labels via the sidebar or gh pr edit 5201 --add-label <label>

PR title tags & labels:
Component tags ([Triton/Gluon], [HIP], [CK], [ASM], ...) are added to the PR title and as PR labels automatically from the changed files and re-synced on every push — change-type tags like [fix]/[Perf], op tags like [MLA], and human labels (ci:*) are left untouched. Add the no-auto-title label to opt this PR out.

[Copilot]

🟢 Approval recommended

The change is narrowly scoped to CI workflow expressions and correctly aligns Docker login behavior with the explicit docker_login input.

Pull request overview

This PR updates the release packaging GitHub Actions workflow to make Docker Hub login explicitly opt-in via a docker_login input, instead of implicitly enabling login on all workflow_dispatch runs.

Changes:

• Added a docker_login boolean input to the manual (workflow_dispatch) trigger for aiter-release.yaml.
• Removed the implicit “workflow_dispatch => docker login” behavior by keying Docker secret selection and DOCKER_LOGIN solely off inputs.docker_login.

File summaries

File	Description
.github/workflows/aiter-release.yaml	Adds explicit docker_login input and gates Docker secret selection/login behavior on that input only.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟡 Changes recommended

The workflow currently lacks a workflow_dispatch-scoped docker_login input, so manual runs cannot explicitly enable Docker login and the new gating will always evaluate false for dispatch runs.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite