rusackas commented on PR #40722: URL: https://github.com/apache/superset/pull/40722#issuecomment-4617510960
Good call on `superset-extensions-cli.yml` — it runs the same 3× Python matrix (`previous`/`current`/`next`) on every PR, so I've folded it into this PR with the identical treatment: `current` only on `pull_request`, full spread on push + nightly. Keeps the "how many Python versions on PRs" policy in one reviewable place. This applies the **current-only** variant (matching the rest of the PR as it stands). If we'd rather go with the **current + previous** compromise I floated above — keeping both shipped runtimes (3.11 + 3.10) gated pre-merge and deferring only `next`/3.12 — I'll switch all four workflows here to that in one go; just say the word. Note: extensions-cli also still does change-detection at the *step* level (unlike the job-level gating in #40718), so it's a candidate for that conversion too — but that's a separate concern and I've left it out of this PR to keep the scope to the Python-version matrix. -- 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]
