Publish to PyPI workflow (RUC-NLPIR/Arbor)

name: Publish to PyPI
 
# Triggered when you push a version tag, e.g.:
#   git tag v0.2.0 && git push origin v0.2.0
# The tag value becomes the published version via setuptools-scm.
on:
  push:
    tags:
      - "v*"
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0  # full history + tags so setuptools-scm can read the version
      - uses: astral-sh/setup-uv@v5
      - name: Build sdist and wheel
        run: uv build
      - uses: actions/upload-artifact@v4
        with:
          name: dist
          path: dist/
 
  publish:
    timeout-minutes: 30
    needs: build
    runs-on: latchkey-small
    environment: pypi          # must match the environment in the PyPI trusted-publisher config
    permissions:
      id-token: write          # required for PyPI Trusted Publishing (OIDC); no token needed
    steps:
      - uses: actions/download-artifact@v4
        with:
          name: dist
          path: dist/
      - uses: pypa/gh-action-pypi-publish@release/v1
 
  github-release:
    timeout-minutes: 30
    needs: publish
    runs-on: latchkey-small
    permissions:
      contents: write          # required to create the GitHub Release
    steps:
      - uses: actions/download-artifact@v4
        with:
          name: dist
          path: dist/
      - name: Check whether a Release already exists for this tag
        id: check
        env:
          GH_TOKEN: ${{ github.token }}
        run: |
          # If you drafted the Release on the web before pushing the tag, it
          # already exists here and has your hand-written notes.
          if gh release view "${GITHUB_REF_NAME}" --repo "${GITHUB_REPOSITORY}" >/dev/null 2>&1; then
            echo "exists=true" >> "$GITHUB_OUTPUT"
          else
            echo "exists=false" >> "$GITHUB_OUTPUT"
          fi
      - name: Create or update GitHub Release
        uses: softprops/action-gh-release@v2
        with:
          # Auto-generate notes ONLY when this workflow is creating the Release
          # (i.e. you pushed a bare tag). If you already wrote notes on the web,
          # we leave them untouched and just attach the build artifacts.
          generate_release_notes: ${{ steps.check.outputs.exists == 'false' }}
          files: dist/*                  # attach the built wheel + sdist to the release