nzw921rx opened a new pull request, #13275: URL: https://github.com/apache/seatunnel/pull/13275
### Purpose of this pull request This contribution to Apache SeaTunnel fixes the Helm publishing startup failure and enables manual publishing of Docker images and Helm charts from an existing release tag. The 3.1.0 Helm workflow failed because `docker/login-action@v3` is not allowed by the ASF Actions policy: https://github.com/apache/seatunnel/actions/runs/43453693668 Changes: - Add a required `tag` input to both manual publishing entry points. - Explicitly check out `refs/tags/<tag>` for manual runs, including both Docker checkout steps. - Allow the Docker publishing job to run manually from `dev`, retaining the upstream-repository restriction. - Pin Helm's Docker login action to the same SHA already used by the Docker publishing workflow. Automatic publishing on tag pushes is preserved. Manual publishing uses the selected tag's sources, allowing an existing release to be published without moving its Git tag or redeploying Maven artifacts. ### Does this PR introduce _any_ user-facing change? No runtime or connector changes. Release managers can manually run either publishing workflow from `dev` by providing an existing release tag. A nonexistent tag or branch-only name fails at checkout. ### How was this patch tested? - `actionlint` 1.7.7 passed for both workflows, with optional ShellCheck/Pyflakes integrations disabled. - YAML checks verified required inputs, existing push-tag filters, repository guards, and checkout refs. - `bash -n` passed for workflow run blocks. - Git reference checks verified tag selection when a same-named branch exists, and rejection of branch-only, nonexistent, and empty tag refs. - `git diff --check` passed. `./mvnw spotless:apply` and `./mvnw -q -DskipTests verify` were attempted but stopped before Maven started because the wrapper could not resolve `repo.maven.apache.org`. No publishing workflow was triggered during validation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
