burr 0.20.0

Design-rule checks for CAD-as-code workflows.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

# Publishing Burr Packages

## Rust CLI

The Rust CLI is published to crates.io as `burr`.

```bash
cargo publish
```

## Python build123d Helper

The Python helper is published to PyPI as `burr-build123d`.

Preferred path: GitHub trusted publishing.

Configure PyPI with a pending publisher:

```txt
PyPI project: burr-build123d
Owner: fraylabs
Repository: burr
Workflow: publish-python.yml
Environment: pypi
```

PyPI must match these GitHub trusted-publishing claims:

```txt
sub: repo:fraylabs/burr:environment:pypi
repository: fraylabs/burr
repository_owner: fraylabs
job_workflow_ref: fraylabs/burr/.github/workflows/publish-python.yml@refs/heads/main
ref: refs/heads/main
environment: pypi
```

Then run the `Publish Python` GitHub Actions workflow with:

```txt
ref: burr-build123d-v0.9.0
```

If publish fails with `invalid-publisher`, the PyPI pending publisher does not
match the claims above.

Local token fallback:

```bash
cp .env.local.example .env.local
# Replace the placeholder with the real PyPI API token.
npm run publish:python:local
npm run publish:python:local -- --confirm
```

The local helper refuses to publish unless `UV_PUBLISH_TOKEN` is set to a real
`pypi-...` token and `--confirm` is passed.

After publishing, verify from a fresh project:

```bash
uv init /tmp/burr-pypi-install-check
cd /tmp/burr-pypi-install-check
uv add burr-build123d
uv run python -c "import burr_build123d; print(burr_build123d.__version__)"
```