From 26d4d3a9b3c59fa22c042d3037e86acb8a695d10 Mon Sep 17 00:00:00 2001
From: Kohsuke Kawaguchi <kk@kohsuke.org>
Date: Tue, 24 Dec 2024 10:12:42 -0800
Subject: [PATCH] Trying to make `pipenv install --dev` work

After a failure at https://github.com/launchableinc/cli/pull/955 I'm
coming in for a minimal bandaid approach.

Also list the packages and their versions so that we can keep track of
how dependencies have resolved.
---
 .github/workflows/python-package.yml | 1 +
 Pipfile                              | 2 ++
 2 files changed, 3 insertions(+)

diff --git a/.github/workflows/python-package.yml b/.github/workflows/python-package.yml
index 4257f2afc..4d0d4bc9e 100644
--- a/.github/workflows/python-package.yml
+++ b/.github/workflows/python-package.yml
@@ -75,6 +75,7 @@ jobs:
           pipenv install --dev --python ${{ matrix.python-version }}
     - name: Build
       run: |
+        pipenv run pip list
         pipenv run build
         pipenv run install
     - name: Type check
diff --git a/Pipfile b/Pipfile
index b915c0b71..c1c23f09f 100644
--- a/Pipfile
+++ b/Pipfile
@@ -28,6 +28,8 @@ types-requests = "*"
 types-tabulate = "*"
 lxml = "<=5.2.2"
 unittest-xml-reporting = "*"
+# newer virtualenv creates a conflict with importlib-metadata. This is the latest version that seems to avoid that
+virtualenv = "==20.16.2"
 
 [packages]
 launchable = {editable = true, path = "."}