Fix trunk-upgrade workflow to use action-provided Trunk binary

[Copilot]

The scheduled Trunk Upgrade workflow failed in job upgrade because trunk was invoked as if it were globally on PATH. In this runner context, trunk-io/trunk-action installs Trunk at TRUNK_PATH, so the upgrade step never found the binary.

• Root cause

  • trunk upgrade -y --include-cli assumed shell PATH resolution.
  • The action exposes Trunk via TRUNK_PATH, not guaranteed PATH injection for later raw run steps.

• Workflow change

  • Updated .github/workflows/trunk-upgrade.yml to invoke Trunk through TRUNK_PATH in the upgrade step.
  • Scope is intentionally minimal: single-line command fix, no behavior changes outside the upgrade job.

• Resulting command shape

  - name: Upgrade Trunk CLI and linters
    run: '"${TRUNK_PATH}" upgrade -y --include-cli'

[Copilot]

Pull request overview

Fixes the scheduled Trunk Upgrade GitHub Actions workflow by invoking the Trunk CLI via the path provided by trunk-io/trunk-action (TRUNK_PATH), ensuring the upgrade job can locate and execute the Trunk binary reliably on the runner.

Changes:

• Update the upgrade step to run Trunk using TRUNK_PATH instead of assuming trunk is on PATH.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.