Skip to content

Update dependency boto3 to v1.34.149 #904

Update dependency boto3 to v1.34.149

Update dependency boto3 to v1.34.149 #904

Workflow file for this run

# based on https://github.com/pantsbuild/example-python/blob/main/.github/workflows/pants.yaml
name: Pants
on: [push, pull_request]
jobs:
org-check:
name: Check GitHub Organization
if: ${{ github.repository_owner == 'fucina' }}
runs-on: ubuntu-20.04
steps:
- name: Noop
run: "true"
build:
name: Perform CI Checks
needs: org-check
env:
PANTS_CONFIG_FILES: pants.ci.toml
runs-on: ubuntu-latest
strategy:
matrix:
python-version: ["3.9"]
steps:
- uses: actions/checkout@v3
- name: Get Pants version
id: pants_version
run: |
# Capture the "pants_version = " line from config.
PANTS_VERSION=$(grep -E '^pants_version\s*=' pants.toml)
echo "::set-output name=pants_version::$PANTS_VERSION"
- uses: actions/cache@v3
id: cache_pants_setup
with:
path: |
~/.cache/pants/setup
key: pants-setup-${{ steps.pants_version.outputs.pants_version }}
- uses: actions/cache@v3
id: cached_named_caches
with:
path: |
~/.cache/pants/named_caches
# The Python backend uses named_caches for Pip/PEX state,
# so it is appropriate to invalidate on requirements.txt changes.
key: pants-named-caches-${{ runner.os }}-${{ hashFiles('pants.toml') }}-${{ hashFiles('requirements.txt') }}
# Note that falling back to a restore key may give a useful partial result that will save time
# over completely clean state, but will cause the cache entry to grow without bound over time.
# See https://pants.readme.io/docs/using-pants-in-ci for tips on how to periodically clean it up.
# Alternatively you may want to avoid using restore keys.
restore-keys: |
pants-named-caches-${{ runner.os }}-${{ hashFiles('pants.toml') }}-${{ hashFiles('requirements.txt') }}
pants-named-caches-${{ runner.os }}-${{ hashFiles('pants.toml') }}-
pants-named-caches-${{ runner.os }}-
# If you're not using a fine-grained remote caching service (see https://www.pantsbuild.org/docs/remote-caching),
# then you may also want to preserve the local Pants cache (lmdb_store). However this must invalidate for
# changes to any file that can affect the build, so may not be practical in larger repos.
# A remote cache service integrates with Pants's fine-grained invalidation and avoids these problems.
- uses: actions/cache@v3
id: cache_lmdb_store
with:
path: |
~/.cache/pants/lmdb_store
key: pants-lmdb-store-${{ runner.os }}-${{ hashFiles('**/*') }}
# Same caveat as above regarding the issues with restore keys.
restore-keys: pants-lmdb-store-${{ runner.os }}-
- name: Setup Python ${{ matrix.python-version }}
uses: actions/setup-python@v4
with:
python-version: ${{ matrix.python-version }}
- name: Bootstrap Pants
run: |
./pants --version
- name: Check BUILD files
run: ./pants tailor --check update-build-files --check
- name: Lint and typecheck
run: |
./pants lint check ::
- name: Test
run: |
./pants test ::
- name: Upload coverage to Codecov
uses: codecov/codecov-action@v3
with:
files: ./dist/coverage/python/coverage.xml
- name: Login to GitHub registry
run: echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u $ --password-stdin
- name: Package / Run
run: |
export GIT_COMMIT=${{ github.sha }}
# We also smoke test that our release process will work by running `package`.
./pants package ::
- name: Publish
run: |
export GIT_COMMIT=${{ github.sha }}
./pants publish ::
if: github.ref == 'refs/heads/main'
- name: Dev Release
uses: "marvinpinto/action-automatic-releases@latest"
with:
repo_token: "${{ secrets.GITHUB_TOKEN }}"
automatic_release_tag: "main"
prerelease: true
title: "Development Build"
files: |
dist/src.treb/bin.pex
if: github.ref == 'refs/heads/main'
- name: Upload pants log
uses: actions/upload-artifact@v3
with:
name: pants-log
path: .pants.d/pants.log
if: always() # We want the log even on failures.