Skip to content

Commit b94e0b5

Browse files
authored
Upgrade to Pants 2.17.0 (#35)
This updates this repo to Pants 2.17, via 2.16. Upgrading to 2.16 requires adjusting for the new approach to tools (no "tool lockfiles").
1 parent ff20d11 commit b94e0b5

File tree

6 files changed

+333
-1045
lines changed

6 files changed

+333
-1045
lines changed

.github/workflows/pants.yaml

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ jobs:
2626
- uses: actions/setup-python@v4
2727
with:
2828
python-version: ${{ matrix.python-version }}
29-
- uses: pantsbuild/actions/init-pants@v4-scie-pants
29+
- uses: pantsbuild/actions/init-pants@v5-scie-pants
3030
# This action bootstraps pants and manages 2-3 GHA caches.
3131
# See: github.com/pantsbuild/actions/tree/main/init-pants/
3232
with:
@@ -35,7 +35,7 @@ jobs:
3535
gha-cache-key: v0
3636
# The Python backend uses named_caches for Pip/PEX state,
3737
# so it is appropriate to invalidate on lockfile changes.
38-
named-caches-hash: ${{ hashFiles('lockfiles/*.txt') }}
38+
named-caches-hash: ${{ hashFiles('lockfiles/*') }}
3939
# If you're not using a fine-grained remote caching service (see https://www.pantsbuild.org/docs/remote-caching),
4040
# then you may also want to preserve the local Pants cache (lmdb_store). However this must invalidate for
4141
# changes to any file that can affect the build, so may not be practical in larger repos.
@@ -50,9 +50,10 @@ jobs:
5050
run: |
5151
pants --version
5252
- name: Check BUILD files
53-
run: pants tailor --check update-build-files --check
53+
run: |
54+
pants tailor --check update-build-files --check ::
5455
- name: Lint and typecheck
55-
run: |
56+
run: |
5657
pants lint check ::
5758
- name: Test
5859
run: |

lockfiles/mypy.lock

Lines changed: 0 additions & 305 deletions
This file was deleted.

0 commit comments

Comments
 (0)