Push table_cls to pypi workflow (RapidAI/TableStructureRec)

The Push table_cls to pypi workflow from RapidAI/TableStructureRec, explained and optimized by Latchkey.

What it does

This is the Push table_cls to pypi workflow from the RapidAI/TableStructureRec repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: Push table_cls to pypi

on:
  push:
    # branches: [ main ]
    # paths:
    #   - 'table_cls/**'
    tags:
      - table_cls_v*

jobs:
  UnitTesting:
    runs-on: ubuntu-latest
    steps:
      - name: Pull latest code
        uses: actions/checkout@v3

      - name: Set up Python 3.10
        uses: actions/setup-python@v4
        with:
          python-version: '3.10'
          architecture: 'x64'

      - name: Display Python version
        run: python -c "import sys; print(sys.version)"

      - name: Unit testings
        run: |
          pip install -r requirements.txt
          pip install pytest beautifulsoup4

          pytest tests/test_table_cls.py

  GenerateWHL_PushPyPi:
    needs: UnitTesting
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v3

      - name: Set up Python 3.10
        uses: actions/setup-python@v4
        with:
          python-version: '3.10'
          architecture: 'x64'

      - name: Run setup.py
        run: |
          pip install -r requirements.txt
          python -m pip install --upgrade pip
          pip install wheel get_pypi_latest_version

          python setup_table_cls.py bdist_wheel "${{ github.ref_name }}"

      - name: Publish distribution 📦 to PyPI
        uses: pypa/gh-action-pypi-publish@v1.5.0
        with:
          password: ${{ secrets.TABLE_CLS }}
          packages_dir: dist/

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: Push table_cls to pypi
 
on:
  push:
    # branches: [ main ]
    # paths:
    #   - 'table_cls/**'
    tags:
      - table_cls_v*
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  UnitTesting:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Pull latest code
        uses: actions/checkout@v3
 
      - name: Set up Python 3.10
        uses: actions/setup-python@v4
        with:
          cache: 'pip'
          python-version: '3.10'
          architecture: 'x64'
 
      - name: Display Python version
        run: python -c "import sys; print(sys.version)"
 
      - name: Unit testings
        run: |
          pip install -r requirements.txt
          pip install pytest beautifulsoup4
 
          pytest tests/test_table_cls.py
 
  GenerateWHL_PushPyPi:
    timeout-minutes: 30
    needs: UnitTesting
    runs-on: latchkey-small
 
    steps:
      - uses: actions/checkout@v3
 
      - name: Set up Python 3.10
        uses: actions/setup-python@v4
        with:
          cache: 'pip'
          python-version: '3.10'
          architecture: 'x64'
 
      - name: Run setup.py
        run: |
          pip install -r requirements.txt
          python -m pip install --upgrade pip
          pip install wheel get_pypi_latest_version
 
          python setup_table_cls.py bdist_wheel "${{ github.ref_name }}"
 
      - name: Publish distribution 📦 to PyPI
        uses: pypa/gh-action-pypi-publish@v1.5.0
        with:
          password: ${{ secrets.TABLE_CLS }}
          packages_dir: dist/
 

What changed

• Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
• Cancel superseded runs when a branch or PR gets a newer push.
• Cache dependency installs on the setup step so they are served from cache.
• Add a job timeout so a hung step cannot burn hours of runner time.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

This workflow runs 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow