Pulled in UV_VENV_CLEAR for uv==0.10.0 break

[jamesbraza]

Sister PR to Future-House/aviary#338

---

Note

Low Risk
CI-only environment-variable change; the main risk is unexpected build/lint behavior changes in GitHub Actions runs.

Overview
Adds UV_VENV_CLEAR=1 to the GitHub Actions environment for the Publish workflow’s publish job and the Lint and Test workflow’s lint job, as a workaround for a hynek/build-and-inspect-python-package/uv venv clearing issue.

^{Written by Cursor Bugbot for commit 2a95c17. Configure here.}

[dosubot]

Related Documentation

Checked 1 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[Copilot]

Pull request overview

Adds a GitHub Actions environment flag to work around a uv==0.10.0-related venv-clearing behavior impacting hynek/build-and-inspect-python-package.

Changes:

• Set UV_VENV_CLEAR=1 for the lint job in CI tests workflow.
• Set UV_VENV_CLEAR=1 for the publish job in release build workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/tests.yml	Adds UV_VENV_CLEAR to the lint job environment to unblock package build/inspect steps.
.github/workflows/build.yml	Adds UV_VENV_CLEAR to the publish job environment to unblock release build/inspect steps.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

UV_VENV_CLEAR is currently set at the job level, which means it will also affect the later uv sync / uv run steps in this job. If the workaround is only needed for hynek/build-and-inspect-python-package, consider moving this env var to just those uses: hynek/build-and-inspect-python-package@v2 steps to avoid unintended behavior changes and extra venv churn for the rest of the lint job.