python-cad-tools 0.1.11__tar.gz → 0.1.13__tar.gz

{python_cad_tools-0.1.11 → python_cad_tools-0.1.13}/.github/workflows/ci.yml

@@ -1,3 +1,22 @@
+# Main CI workflow: runs the full test/quality/packaging suite on
+# every PR and on push to main, and is also the ONE place that
+# publishes to PyPI.
+#
+# Publishing happens only in the `build-publish` job, gated behind
+# every other job via `needs:` and only when the ref being tested is
+# a "v*" tag (see the `if:` on that job). release.yml creates that
+# tag but pushes it using the default GITHUB_TOKEN, and GitHub does
+# not start new workflow runs from GITHUB_TOKEN-authored pushes (its
+# anti-recursion rule) — so the tag push alone won't reach this file.
+# Instead release.yml explicitly dispatches this workflow against the
+# new tag via `workflow_dispatch` below, which IS exempt from that
+# rule. `workflow_dispatch` is included here for that purpose (and
+# lets you manually re-run CI against any existing tag/ref by hand).
+#
+# release.yml itself does not build or publish anything — it only
+# creates the tag and triggers this run. Keeping publish logic in one
+# gated place (instead of duplicating it in release.yml) avoids two
+# workflows racing to publish the same version.
 name: CI
 
 on:
@@ -5,11 +24,14 @@ on:
     branches: [main]
     tags: ['v*']
   pull_request:
+  workflow_dispatch:
 
 permissions:
   contents: read
 
 jobs:
+  # Fastest signal: static checks plus unit/typing tests, so obvious
+  # problems fail before the slower jobs below even start.
   lint-type-unit:
     name: Lint, type, unit
     runs-on: ubuntu-latest
@@ -25,6 +47,8 @@ jobs:
       - run: mypy
       - run: pytest tests/unit tests/typing -q
 
+  # Integration tests against the real CAD/BIM/mesh/drawing exporter
+  # libraries (not mocked) to catch toolchain-level breakage.
   exporter-integration:
     name: Exporter integration
     runs-on: ubuntu-latest
@@ -38,6 +62,8 @@ jobs:
       - run: pip install -e '.[dev]'
       - run: pytest tests/integration -q
 
+  # Builds the TypeScript viewer and runs its unit + headless-browser
+  # (Playwright) end-to-end tests.
   viewer-browser:
     name: Viewer and browser tests
     runs-on: ubuntu-latest
@@ -65,6 +91,9 @@ jobs:
       - working-directory: viewer
         run: npm run test:e2e
 
+  # Builds the wheel and sdist, validates them with twine, and runs
+  # packaging-specific tests — catches issues the editable install
+  # used elsewhere in CI wouldn't surface.
   wheel-sdist:
     name: Wheel and sdist inspection
     runs-on: ubuntu-latest
@@ -80,6 +109,9 @@ jobs:
       - run: python -m twine check dist/*
       - run: pytest tests/packaging -q
 
+  # Installs the built wheel into a fresh venv (non-editable, unlike
+  # the rest of CI) and runs a generic project through the CLI —
+  # catches packaging omissions an editable install would hide.
   clean-install:
     name: Clean non-editable install
     runs-on: ubuntu-latest
@@ -104,6 +136,8 @@ jobs:
           /tmp/clean-venv/bin/python-cad build --project-root /tmp/generic-project
           /tmp/clean-venv/bin/python-cad verify --project-root /tmp/generic-project
 
+  # End-to-end CLI smoke test on an editable install: init, build,
+  # verify, clean.
   generic-e2e:
     name: Generic E2E
     runs-on: ubuntu-latest
@@ -122,6 +156,7 @@ jobs:
           python-cad verify --project-root /tmp/e2e-project
           python-cad clean --project-root /tmp/e2e-project
 
+  # Guards against unintentional breaking changes to the public API.
   public-api:
     name: Public API surface
     runs-on: ubuntu-latest
@@ -135,6 +170,8 @@ jobs:
       - run: pip install -e '.[dev]'
       - run: pytest tests/unit/test_public_api.py -q
 
+  # Fails if legacy/retired naming from a prior repo migration
+  # reappears in tracked source (see EXCLUDES below for what's exempt).
   active-terminology:
     name: Active terminology scan
     runs-on: ubuntu-latest
@@ -157,6 +194,9 @@ jobs:
           fi
           echo "No active legacy concepts found."
 
+  # Enforces repository layout policy: legacy files/dirs stay absent,
+  # required symlinks (CLAUDE.md -> AGENTS.md) exist, backups stay
+  # untracked, and the expected workflow files are present.
   tree-shape:
     name: Tree shape and policy checks
     runs-on: ubuntu-latest
@@ -187,6 +227,9 @@ jobs:
           done
           echo "All tree shape checks passed."
 
+  # Confirms init/build works on Linux, macOS, and Windows. Windows
+  # skips ruff/mypy since static checks aren't part of the
+  # cross-platform contract, just the CLI behavior.
   supported-platforms:
     name: Supported platforms (${{ matrix.os }})
     strategy:
@@ -218,6 +261,9 @@ jobs:
           python-cad build --project-root C:\platform-test
         if: matrix.os == 'windows-latest'
 
+  # Generates a per-OS `pip freeze` lockfile as a downloadable
+  # artifact for reference. Informational only — not enforced or
+  # committed anywhere automatically.
   platform-locks:
     name: Platform lock generation (${{ matrix.os }})
     strategy:
@@ -250,6 +296,10 @@ jobs:
           name: ${{ matrix.lock }}
           path: ${{ matrix.lock }}
 
+  # Confirms every optional dependency group (cad, bim, mesh, ...)
+  # installs cleanly and imports across OS/Python combinations. PRs
+  # only run a fast subset (core+all on ubuntu/py3.13) via the gate
+  # step below; main and tag pushes run the full matrix.
   toolchain-matrix:
     name: Toolchain matrix (${{ matrix.os }}, py${{ matrix.python }}, ${{ matrix.group }})
     strategy:
@@ -368,9 +418,17 @@ jobs:
           name: toolchain-compatibility-${{ matrix.os }}-py${{ matrix.python }}-${{ matrix.group }}
           path: toolchain-compatibility.json
 
+  # THE publish step for this repo — only runs when the ref under
+  # test is a "v*" tag, and only after every job above has passed
+  # (see `needs:`). Checking the ref rather than the event name lets
+  # this fire both from a direct tag push and from release.yml's
+  # workflow_dispatch trigger (see the file header for why dispatch
+  # is needed). Tags are created by the separate "Release" workflow
+  # (release.yml); nothing else in this repo should build or publish
+  # to PyPI.
   build-publish:
     name: Build and publish to PyPI
-    if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')
+    if: startsWith(github.ref, 'refs/tags/v')
     needs:
       - lint-type-unit
       - exporter-integration
@@ -412,9 +470,11 @@ jobs:
           TWINE_USERNAME: __token__
           TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
 
+  # Generates a SLSA build provenance attestation for the artifacts
+  # build-publish just uploaded, for supply-chain verifiability.
   provenance:
     name: Generate SLSA provenance
-    if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')
+    if: startsWith(github.ref, 'refs/tags/v')
     needs: [build-publish]
     permissions:
       actions: read

{python_cad_tools-0.1.11 → python_cad_tools-0.1.13}/.github/workflows/downstream-compatibility.yml

@@ -1,3 +1,9 @@
+# Placeholder for testing python-cad-tools wheels against a future
+# downstream "companion repository" (not yet created). It intentionally
+# always fails (exit 1) — that's not a bug, it's a guard against this
+# check silently being treated as passing before it's actually
+# implemented. Do not run it or remove the exit 1 until a companion
+# repository exists at the URL you'd pass in.
 name: Downstream compatibility
 
 on:

{python_cad_tools-0.1.11 → python_cad_tools-0.1.13}/.github/workflows/release-candidate.yml

@@ -1,3 +1,11 @@
+# Release candidate: builds and verifies a pre-release artifact for
+# manual QA WITHOUT publishing anything to PyPI or pushing any tag.
+# Use this to sanity-check a wheel/sdist before running the real
+# "Release" workflow (release.yml), which does publish.
+#
+# To run: Actions -> Release candidate -> Run workflow, with a label
+# for this candidate (e.g. "0.1.0rc1"). Download the built artifact
+# from the "build" job's summary page to test it locally.
 name: Release candidate
 
 on:
@@ -12,6 +20,9 @@ permissions:
   contents: read
 
 jobs:
+  # Builds the wheel/sdist after lint/type/unit checks pass, and
+  # uploads them as a workflow artifact (90-day retention). Nothing
+  # is published here.
   build:
     name: Build wheel and sdist
     runs-on: ubuntu-latest
@@ -54,6 +65,9 @@ jobs:
           path: dist/
           retention-days: 90
 
+  # Re-downloads the build job's artifact, re-verifies its hashes, and
+  # installs it non-editably — catches artifact corruption or a
+  # mismatch between what "build" produced and what got uploaded.
   verify:
     name: Verify candidate hashes
     runs-on: ubuntu-latest

python_cad_tools-0.1.13/.github/workflows/release.yml

@@ -0,0 +1,61 @@
+# Release: cuts a new version by tagging `main`. Manual trigger only.
+#
+# This workflow does NOT build or publish anything itself — it only
+# creates a "v*" tag and hands off to ci.yml's `build-publish` job,
+# which is the single, test-gated path to PyPI. Keeping build/publish
+# out of this file avoids two workflows racing to publish the same
+# version.
+#
+# The hand-off can't just be "push the tag": pushes made with the
+# default GITHUB_TOKEN (used below via actions/checkout) don't start
+# other workflow runs — that's a deliberate GitHub anti-recursion
+# rule, not a bug. GitHub exempts workflow_dispatch from that rule, so
+# the last step here explicitly dispatches ci.yml against the new tag
+# using that same GITHUB_TOKEN. No extra token/secret is needed.
+#
+# To run: Actions -> Release -> Run workflow, with the version to
+# release (e.g. "0.1.13", no "v" prefix). Then watch the "CI" workflow
+# run that starts against the new tag — that run is the actual publish.
+name: Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: "Version to release (e.g. 0.1.2)"
+        required: true
+        type: string
+
+permissions:
+  contents: write
+  actions: write
+
+jobs:
+  release:
+    name: Tag and push release
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          fetch-depth: 0
+
+      - name: Check version is not already published
+        run: |
+          version="${{ inputs.version }}"
+          status=$(curl -s -o /dev/null -w "%{http_code}" "https://pypi.org/pypi/python-cad-tools/${version}/json")
+          if [ "$status" = "200" ]; then
+            echo "::error::python-cad-tools ${version} is already published on PyPI. This looks like a duplicate release attempt (a previous run likely already tagged and uploaded it) — choose a new version instead of re-running with the same one."
+            exit 1
+          fi
+
+      - name: Create and push tag
+        run: |
+          git config user.name "github-actions"
+          git config user.email "github-actions@github.com"
+          git tag "v${{ inputs.version }}"
+          git push origin "v${{ inputs.version }}"
+
+      - name: Trigger CI publish run for the new tag
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: gh workflow run ci.yml --repo "${{ github.repository }}" --ref "v${{ inputs.version }}"

{python_cad_tools-0.1.11/src/python_cad_tools.egg-info → python_cad_tools-0.1.13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-cad-tools
-Version: 0.1.11
+Version: 0.1.13
 Summary: Typed, headless Python tooling for CAD/BIM models and artifacts
 Author: Brandon Benge
 License: AGPL-3.0-only

{python_cad_tools-0.1.11 → python_cad_tools-0.1.13/src/python_cad_tools.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-cad-tools
-Version: 0.1.11
+Version: 0.1.13
 Summary: Typed, headless Python tooling for CAD/BIM models and artifacts
 Author: Brandon Benge
 License: AGPL-3.0-only

{python_cad_tools-0.1.11 → python_cad_tools-0.1.13}/src/python_cad_tools.egg-info/scm_version.json

@@ -1,7 +1,7 @@
 {
-  "tag": "0.1.11",
+  "tag": "0.1.13",
   "distance": 0,
-  "node": "gcd8e40749ec366cae0576b2e4fc630c15e97f638",
+  "node": "g88544bff4c35b1b804776231bf4db8aac1b5c5f1",
   "dirty": false,
   "branch": "HEAD",
   "node_date": "2026-08-11"

python_cad_tools-0.1.11/.github/workflows/release.yml

@@ -1,51 +0,0 @@
-name: Release
-
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: "Version to release (e.g. 0.1.2)"
-        required: true
-        type: string
-
-permissions:
-  contents: write
-  id-token: write
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - uses: actions/setup-python@v5
-        with:
-          python-version: "3.13"
-
-      - name: Check version is not already published
-        run: |
-          version="${{ inputs.version }}"
-          status=$(curl -s -o /dev/null -w "%{http_code}" "https://pypi.org/pypi/python-cad-tools/${version}/json")
-          if [ "$status" = "200" ]; then
-            echo "::error::python-cad-tools ${version} is already published on PyPI. This looks like a duplicate release attempt (a previous run likely already tagged and uploaded it) — choose a new version instead of re-running with the same one."
-            exit 1
-          fi
-
-      - name: Create and push tag
-        run: |
-          git config user.name "github-actions"
-          git config user.email "github-actions@github.com"
-          git tag "v${{ inputs.version }}"
-          git push origin "v${{ inputs.version }}"
-
-      - name: Build distribution
-        run: |
-          pip install build
-          python -m build
-
-      - name: Upload to PyPI
-        uses: pypa/gh-action-pypi-publish@v1.10.3
-        with:
-          password: ${{ secrets.PYPI_TOKEN }}