From 1cefd59ecaa98e054f0a55405db0f1128af4666c Mon Sep 17 00:00:00 2001 From: "Kyle D. McCormick" Date: Mon, 10 Jun 2024 11:36:12 -0400 Subject: [PATCH] temp: build: compile python requirements with 3.8, not 3.11 We haven't quite dropped 3.8 support yet, so we can't use these workflows if they're compiling with 3.11 Revert this commit when we drop 3.8 support. WIP: how do we tell the upgrade requirements workflow to use 3.8? --- .github/workflows/compile-python-requirements.yml | 2 +- .github/workflows/upgrade-one-python-dependency.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/compile-python-requirements.yml b/.github/workflows/compile-python-requirements.yml index 0ff99b9c685a..fda1d3b33812 100644 --- a/.github/workflows/compile-python-requirements.yml +++ b/.github/workflows/compile-python-requirements.yml @@ -26,7 +26,7 @@ jobs: - name: Set up Python environment uses: actions/setup-python@v5 with: - python-version: "3.11" + python-version: "3.8" - name: Run make compile-requirements env: diff --git a/.github/workflows/upgrade-one-python-dependency.yml b/.github/workflows/upgrade-one-python-dependency.yml index 6ca5dfcb355e..baed246246a0 100644 --- a/.github/workflows/upgrade-one-python-dependency.yml +++ b/.github/workflows/upgrade-one-python-dependency.yml @@ -39,7 +39,7 @@ jobs: - name: Set up Python environment uses: actions/setup-python@v5 with: - python-version: "3.11" + python-version: "3.8" - name: Update any pinned dependencies env: