Skip to content

fix: use which uv in "Expose uv in workspace" step instead of step output reference#1385

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-github-actions-job-run-agent
Draft

fix: use which uv in "Expose uv in workspace" step instead of step output reference#1385
Copilot wants to merge 2 commits into
mainfrom
copilot/fix-github-actions-job-run-agent

Conversation

Copilot AI commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

The run / agent job in workflows using uvx-based MCP servers (e.g. Code Duplication Detector, Code Complexity Detector) was failing with:

ln: failed to create symbolic link '/opt/hostedtoolcache/gh-aw-tools/current/x64/bin/uv' -> '': No such file or directory

Root cause: When the gh-aw compiler detects a uvx MCP server, it emits an unconditional Setup uv step without id: setup-uv. The Expose uv in workspace step in runtime-setup.md referenced ${{ steps.setup-uv.outputs.uv-path }}, which evaluates to empty string when the step has no matching ID — causing ln -sf "" to fail.

Fix:

  • runtime-setup.md: replace env: UV_PATH: ${{ steps.setup-uv.outputs.uv-path }} + ln -sf "$UV_PATH" with ln -sf "$(which uv)" — robust regardless of which step installed uv or whether it carries id: setup-uv
  • All 57 compiled lock files regenerated via make compile

The `Expose uv in workspace` step in the runtime-setup.md fragment used
`${{ steps.setup-uv.outputs.uv-path }}` to find the uv binary path. When
the gh-aw compiler emits its own unconditional `Setup uv` step (for
workflows that use uvx MCP servers like code-duplication-detector and
code-complexity-detector), it omits `id: setup-uv`, making the step
output reference resolve to an empty string.

Fix: use `$(which uv)` instead, which works regardless of how uv was
installed. Regenerate all lock files accordingly.
Copilot AI changed the title [WIP] Fix failing GitHub Actions job run / agent fix: use which uv in "Expose uv in workspace" step instead of step output reference Jun 23, 2026
Copilot finished work on behalf of v1v June 23, 2026 13:49
Copilot AI requested a review from v1v June 23, 2026 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants