sadpandajoe commented on code in PR #45183:
URL: https://github.com/apache/superset/pull/45183#discussion_r4241014486


##########
Dockerfile:
##########
@@ -18,7 +18,7 @@
 ######################################################################
 # Node stage to deal with static asset construction
 ######################################################################
-ARG PY_VER=3.11-slim-trixie
+ARG PY_VER=3.12-slim-trixie

Review Comment:
   This makes 3.12 the Python the default image ships, but the backend CI jobs 
still resolve `current` to 3.11 (`.github/actions/setup-backend/action.yml`) 
and the only other version exercised is `next` (3.13). So nothing in unit or 
integration CI runs on 3.12, and a 3.12-only break in the shipped runtime would 
first show up in the published image rather than on a PR. Should `current` move 
to 3.12 in this change, or is there another job that runs the backend suite on 
3.12?



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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to