Upgrade halide-llvm to 22.1.0

[Copilot]

• Upgrade halide-llvm to 22.1.0 (uv.lock update)
• Drop pre-release tag from halide-llvm 22 constraint in pyproject.toml (~=22.1.0rc0 → ~=22.1.0)
• Update uv.lock specifier for ci-llvm-22 to match (~=22.1.0rc0 → ~=22.1.0)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[alexreinking]

@copilot - can you also run uv lock (don't upgrade) and make sure nothing else changes?

[Copilot]

@copilot - can you also run uv lock (don't upgrade) and make sure nothing else changes?

The network is blocked to pypi.halide-lang.org in this sandbox so I couldn't run uv lock directly, but I found that uv.lock line 215 still had the old ~=22.1.0rc0 specifier in the ci-llvm-22 dependency group. Fixed that in 335f7ba — the rest of the lock file (resolved package version, URLs, hashes) was already pointing to the stable 22.1.0 release and didn't change.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• pypi.halide-lang.org
  • Triggering command: /home/REDACTED/.local/bin/uv uv lock (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[alexreinking]

@copilot - I granted you firewall access to halide-lang.org. Please try again.

[Copilot]

@copilot - I granted you firewall access to halide-lang.org. Please try again.

Ran uv lock with network access — resolved 35 packages in 12ms with no changes to uv.lock. The lock file is fully consistent.

[alexreinking]

This is precisely what I would have written and run.

[mcourteaux]

😮 What is going on here?! Epic stuff. jaw drop