karthik-0306 opened a new pull request, #12994:
URL: https://github.com/apache/seatunnel/pull/12994

   ### Purpose of this pull request
   
   Follow-up to #12857, related to #12707. This PR contributes a CI fix to 
Apache SeaTunnel.
   
   `ubuntu-latest` now points to Ubuntu 26.04, and `actions/setup-python` has 
no Python 3.9 build for it, so the `Test with Python 3.9` job in 
`.github/workflows/python-sdk.yml` fails at "Set up Python" for every SDK pull 
request ("The version '3.9' with architecture 'x64' was not found for Ubuntu 
26.04", seen on #12858). In the `actions/python-versions` manifest, 3.9.25 has 
Linux x64 builds for Ubuntu 22.04 and 24.04 only, while 3.10 and 3.13 also have 
26.04 builds.
   
   This pins the job to `ubuntu-24.04`, which has both 3.9 and 3.13. 3.9 is 
still the `python_requires` floor in `tools/seatunnel-python-sdk/setup.py`, so 
dropping it from the matrix would stop testing the declared minimum.
   
   If you'd rather raise the SDK's minimum Python to 3.10 instead of pinning 
the runner, I'm happy to change this PR to that; I kept 3.9 because it is still 
the declared `python_requires` floor.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. CI only.
   
   ### How was this patch tested?
   
   - Checked the `actions/python-versions` manifest: Python 3.9 is available 
for `ubuntu-24.04`.
   - Validated the YAML locally (`runs-on: ubuntu-24.04`, matrix unchanged: 3.9 
and 3.13).
   - The SDK suite passes locally on Linux with Python 3.9, 3.10 and 3.13.
   - This PR changes the workflow file, so the workflow runs on this PR itself 
once a maintainer approves the run.
   
   ### Check list
   
   * [ ] If any new Jar binary package adding in your PR, please add License 
Notice according
     [New License 
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
   * [ ] If necessary, please update the documentation to describe the new 
feature. https://github.com/apache/seatunnel/tree/dev/docs
   * [ ] If necessary, please update `incompatible-changes.md` to describe the 
incompatibility caused by this PR.
   * [ ] If you are contributing the connector code, please check that the 
following files are updated:
     1. Update 
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
 and add new connector information in it
     2. Update the pom file of 
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
     3. Add ci label in 
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
     4. Add e2e testcase in 
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
     5. Update connector 
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
   


-- 
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]

Reply via email to