autocad-mcp-pro/.github/workflows/ci.yml

name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]
  workflow_dispatch:

concurrency:
  group: ci-${{ github.ref }}
  cancel-in-progress: true

# Two deliberately different installation paths run in this file:
#
#   lint / test-*  install from uv.lock with `--locked`. Every version, down to
#                  the transitive graph, is the one the suite was last run
#                  against; `--locked` *fails* rather than re-resolving if
#                  uv.lock has drifted from pyproject.toml. A release upstream
#                  can no longer turn main red on its own schedule.
#   package        installs the built wheel with plain pip, from the dependency
#                  ranges in pyproject.toml — on purpose. That is the path a
#                  user gets from PyPI, and it is the only job that exercises
#                  it, so it must not be locked.
#
# Locked CI is blind to upstream drift by construction; deps-floating.yml is the
# deliberate counterweight that resolves the ranges fresh on a schedule.
env:
  # Pinned for the same reason ruff is: the tool that reads the lockfile is part
  # of the reproducible environment. Bump this and re-run `uv lock` together.
  LOCKED_UV_VERSION: "0.12.1"

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: "3.11"
      - run: pip install "uv==${{ env.LOCKED_UV_VERSION }}"
      # Dev group only: ruff comes from the lock, the project is not built.
      # The ruff version lives in [dependency-groups] dev in pyproject.toml and
      # nowhere else — the formatter's output changes between minors, so a
      # floating ruff fails `ruff format --check .` on unchanged code.
      - run: uv sync --locked --only-group dev
      - run: uv run --no-sync ruff check .
      - run: uv run --no-sync ruff format --check .

  test-linux:
    runs-on: ubuntu-latest
    strategy:
      fail-fast: false
      matrix:
        python-version: ["3.11", "3.12"]
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        id: python
        with:
          python-version: ${{ matrix.python-version }}
      - run: pip install "uv==${{ env.LOCKED_UV_VERSION }}"
      - name: Install the locked environment
        # uv.lock is a universal resolution over requires-python >=3.11, so the
        # same file serves both matrix legs; --python keeps uv on the
        # interpreter setup-python just provisioned instead of picking its own.
        run: uv sync --locked --extra pdf --python "${{ steps.python.outputs.python-path }}"
      - name: Run tests
        run: uv run --no-sync pytest --cov=. --cov-report=xml --cov-report=term-missing -v
      - name: Upload coverage
        if: matrix.python-version == '3.11'
        uses: actions/upload-artifact@v4
        with:
          name: coverage-report
          path: coverage.xml

  test-windows:
    # Windows leg exercises the mocked-COM suite on the platform the COM
    # backend actually targets (pywin32 installs; no live AutoCAD needed).
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        id: python
        with:
          python-version: "3.11"
      - run: pip install "uv==${{ env.LOCKED_UV_VERSION }}"
      - name: Install the locked environment
        run: uv sync --locked --extra full --python "${{ steps.python.outputs.python-path }}"
      - name: Run tests
        run: uv run --no-sync pytest -v

  package:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: "3.11"
      - name: Build sdist and wheel
        run: |
          pip install build twine
          python -m build
          twine check dist/*
      # Unlocked on purpose: this resolves the published dependency ranges the
      # way a user's `pip install autocad-mcp-pro` does. Locking it would mean
      # nothing in CI ever proves those ranges are installable.
      - name: Install wheel in a clean venv and smoke test
        run: |
          python -m venv /tmp/smoke
          /tmp/smoke/bin/pip install dist/*.whl
          /tmp/smoke/bin/autocad-mcp --help
          /tmp/smoke/bin/python -c "import server, config, security, version, backends, engineering; print('wheel ok', version.__version__)"
      - name: Upload distributions
        uses: actions/upload-artifact@v4
        with:
          name: dist
          path: dist/

  docker:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Build image
        run: docker build -t autocad-mcp:ci .
      - name: Smoke test image
        run: docker run --rm autocad-mcp:ci python -c "import server, engineering.gear, version; print('docker ok', version.__version__)"

  registry-validate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: "3.11"
      - name: Validate server.json against MCP registry schema
        if: ${{ hashFiles('server.json') != '' }}
        run: |
          pip install check-jsonschema
          check-jsonschema --schemafile https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json server.json