(texera) branch gh-readonly-queue/main/pr-8004-97e3585a6ac7aadbea629e7350a96d1a84f7b51c created (now fc32e37054)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-merge-queue[bot] pushed a change to branch gh-readonly-queue/main/pr-8004-97e3585a6ac7aadbea629e7350a96d1a84f7b51c
in repository https://gitbox.apache.org/repos/asf/texera.git


      at fc32e37054 ci: freeze setup-python interpreter (#8004)

This branch includes the following new commits:

     new fc32e37054 ci: freeze setup-python interpreter (#8004)

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

(texera) 01/01: ci: freeze setup-python interpreter (#8004)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/main/pr-8004-97e3585a6ac7aadbea629e7350a96d1a84f7b51c
in repository https://gitbox.apache.org/repos/asf/texera.git

commit fc32e37054083852974e10a56cfb86ebf0562a16
Author: anthonychengit <an...@gmail.com>
AuthorDate: Thu Aug 27 04:52:20 2026 +0000

    ci: freeze setup-python interpreter (#8004)
    
    ### What changes were proposed in this PR?
    
    Prevent Renovate from independently raising the Python interpreter used
    by GitHub Actions while the CI data stack remains pinned to older
    pandas, NumPy, and PyArrow releases.
    
    ```text
    Before: setup-python bump -> interpreter may outrun frozen package wheels -> CI install failure
    After:  interpreter stays frozen -> interpreter and data packages are upgraded together manually
    ```
    
    The rule is narrowly scoped to the `github-actions` manager and
    Renovate's `python` dependency name. Other GitHub Actions updates remain
    enabled and grouped as before.
    
    ### Any related issues, documentation, discussions?
    
    Closes #7720.
    
    ### How was this PR tested?
    
    The regression check was written before the config change and initially
    failed because no setup-python freeze rule existed. After the change:
    
    ```text
    npx --yes --package renovate@44.46.4 renovate-config-validator .github/renovate.json5
    git diff --check
    ```
    
    Result: Renovate reported `Config validated successfully against 1
    file(s)`, and the diff check passed.
    
    ### Was this PR authored or co-authored using generative AI tooling?
    
    Generated-by: Codex was used for implementation and verification
    assistance. I reviewed the final code and test output before submission.
---
 .github/renovate.json5 | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/.github/renovate.json5 b/.github/renovate.json5
index c6fe7f387a..69331ac2ec 100644
--- a/.github/renovate.json5
+++ b/.github/renovate.json5
@@ -150,6 +150,15 @@
       groupName: 'pyamber minor updates',
     },
 
+    // The Python interpreter selects the wheels used by the frozen
+    // pandas/numpy/pyarrow data path below. Upgrade it manually with those
+    // packages so setup-python cannot move CI beyond their published wheels.
+    {
+      matchManagers: ['github-actions'],
+      matchDepNames: ['python'],
+      enabled: false,
+    },
+
     // GitHub Actions bumps in one group, scoped as chore(deps, ci).
     {
       matchManagers: ['github-actions'],