davidzollo opened a new pull request, #12550: URL: https://github.com/apache/seatunnel/pull/12550
## What does this PR do? - Uses the native GitHub Actions workflow ref selector as the Docker release source. - Removes the separate release_tag text input and its duplicate remote-tag validation. - Allows the publishing job to run only when the selected or pushed ref is a tag. - Lets actions/checkout resolve the selected or pushed tag directly from the workflow event. ## Why is the change needed? The manual workflow currently runs from dev and accepts a second release_tag value. This produces two independent release selections and labels the run with dev even though checkout is later redirected to a tag. The workflow ref selector should be the single source of truth. A branch-selected manual run is now skipped before registry login, while a tag-selected run checks out that exact tag. ## Compatibility and scope - Existing tag-push behavior is unchanged. - This native manual-dispatch path applies to tags created after this change is merged, or existing tags whose own workflow already contains workflow_dispatch. - The current v3.0.0 tag does not contain workflow_dispatch, so GitHub cannot select it through Use workflow from. This PR does not rewrite or recreate that release tag. ## Verification - ./mvnw spotless:apply -nsu -Dmaven.gitcommitid.skip=true -T 3C - git diff --check - YAML syntax parsing with Ruby YAML - actionlint v1.7.7 passed for the changed workflow logic after excluding the pre-existing actions/setup-java@v2 age diagnostic - Independent Maintainer Review: passed with no remaining code blockers No local compilation, unit tests, Docker publishing, or runtime execution was performed, following the SeaTunnel local validation policy. GitHub CI remains the runtime merge gate. -- 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]
