build_wheels.yml

name: Build wheels

on: workflow_dispatch

jobs:
  build_sdist:
    name: Build source distribution
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0 # Fetch full history, necessary for git describe in setup.py

      - name: Build sdist
        run: pipx run build --sdist

      - uses: actions/upload-artifact@v4
        with:
          name: cibw-sdist
          path: dist/*.tar.gz

  build_wheels:
    name: Build wheels on ${{ matrix.os }}
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        # macos-13 is an intel runner, macos-14 is apple silicon
        os: [ubuntu-latest, macos-13, macos-14]

    steps:
      - uses: actions/setup-python@v5
        with:
          python-version: 3.8
        if: runner.os == 'macOS' && runner.arch == 'ARM64'

      - uses: actions/checkout@v4
        with:
          fetch-depth: 0 # Fetch full history, necessary for git describe in setup.py

      - name: Checkout charm_src # is this best practice? should we use a submodule?
        uses: actions/checkout@v4
        with:
          repository: charmplusplus/charm
          # token: ${{ secrets.GITHUB_TOKEN }}
          path: charm_src/charm
          fetch-depth: 0 # Fetch full history, necessary for commit_str parsing in setup.py

      - name: Checkout charm_src # is this best practice? should we use a submodule?
        uses: actions/checkout@v4
        with:
          repository: charmplusplus/charm
          token: ${{ secrets.GITHUB_TOKEN }}
          path: charm_src/charm
          fetch-depth: 0 # Fetch full history, necessary for commit_str parsing in setup.py

      - name: Build wheels
        env:
          CIBW_SKIP: "*-manylinux_i686 *-manylinux_ppc64le *-manylinux_s390x *musllinux_*"
        uses: pypa/cibuildwheel@v2.20.0

      - uses: actions/upload-artifact@v4
        with:
          name: cibw-wheels-${{ matrix.os }}-${{ strategy.job-index }}
          path: ./wheelhouse/*.whl