Update Python version to 3.14.7 - #8456

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== candidate files =="
git ls-files | rg '(^\.github/workflows/upgrade-pylib\.lock\.ya?ml$|^\.github/workflows/upgrade-pylib\.md$|upgrade-pylib)' || true

echo
echo "== workflow lock excerpt =="
if [ -f .github/workflows/upgrade-pylib.lock.yml ]; then
  nl -ba .github/workflows/upgrade-pylib.lock.yml | sed -n '1,180p'
elif [ -f .github/workflows/upgrade-pylib.lock.yaml ]; then
  nl -ba .github/workflows/upgrade-pylib.lock.yaml | sed -n '1,180p'
fi

echo
echo "== markdown generator excerpt =="
if [ -f .github/workflows/upgrade-pylib.md ]; then
  nl -ba .github/workflows/upgrade-pylib.md | sed -n '1,180p'
fi

echo
echo "== searches for restore-keys and cp/lib/version checks =="
rg -n "PYTHON_VERSION|restore-keys|cpython/|v3\.14\.7|v3\.14\.6|CACHED|cache-key|cp/Lib|setup-python" .github/workflows || true

Repository: RustPython/RustPython

Length of output: 408

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow lock excerpt =="
awk 'NR>=1 && NR<=180 { printf "%6d  %s\n", NR, $0 }' .github/workflows/upgrade-pylib.lock.yml

echo
echo "== markdown generator excerpt =="
awk 'NR>=1 && NR<=180 { printf "%6d  %s\n", NR, $0 }' .github/workflows/upgrade-pylib.md

echo
echo "== targeted text search =="
grep -RInE "PYTHON_VERSION|restore-keys|cpython/|v3\.14\.7|v3\.14\.6|CACHED|cache-key|cp/Lib|RUSTPY|python|setup-python|git clone|checkout" .github/workflows || true

Repository: RustPython/RustPython

Length of output: 34771

🌐 Web query:

GitHub Actions caching restore-keys partial-match cache key documentation

💡 Result:

In GitHub Actions, the restore-keys input is used to specify a list of alternative keys that the cache action searches if no exact match is found for the primary key [1][2]. How partial matching works: 1. Sequential Search: When an exact match for the primary key is not found, the cache action evaluates the restore-keys in the order they are listed [1][3]. 2. Prefix Matching: A restore key acts as a prefix-match wildcard [4]. If you provide a restore key such as npm-feature-, it will match any existing cache key that begins with that string [1][3]. 3. Selecting the Best Match: If multiple caches exist that match a given restore key (via prefix matching), the action selects the most recently created cache [1][3]. 4. Output: When a partial match is found and restored via restore-keys, the cache-hit output variable will be set to false, indicating that no exact match occurred [5][2]. Example Usage: If your primary key is npm-feature-${{ hashFiles('package-lock.json') }}, you can provide multiple, increasingly general restore-keys to ensure the most relevant available cache is restored [1][3]: restore-keys: | npm-feature-${{ hashFiles('package-lock.json') }} npm-feature- npm- In this scenario, if the specific hash does not match, the action attempts to find any cache starting with npm-feature-, and finally falls back to any cache starting with npm- [1][3].

Citations:

• 1: https://docs.github.com/en/actions/reference/workflows-and-actions/dependency-caching
• 2: https://github.com/actions/cache/blob/main/README.md
• 3: https://github.com/github/docs/blob/main/content/actions/reference/workflows-and-actions/dependency-caching.md
• 4: What does `restore-keys` do? actions/cache#578
• 5: https://github.com/actions/cache/blob/main/restore/README.md