🔧 fix: bump DAGGER_VERSION 0.20.6 → 0.20.8 in CI workflows

[yeazelm]

Summary

• The CLI installed by dagger-for-github no longer round-trips cleanly with the current daggerverse modules at v0.20.6. The version handshake fails before dagger call reaches user code.
• Bumps DAGGER_VERSION to 0.20.8 across the workflows, matching the rest of the org repos (e.g. paper PR #40) that have already moved.

Refs PCC-543

Test plan

• CI / PR / release workflows pass on this PR

[linear-code]

PCC-543

[greptile-apps]

Greptile Summary

Bumps DAGGER_VERSION from 0.20.6 to 0.20.8 in the PR workflow to resolve a version handshake failure between the CLI installed by dagger-for-github and the daggerverse modules used in CI.

• Single-line change in .github/workflows/pr.yaml updating the DAGGER_VERSION env var from \"0.20.6\" to \"0.20.8\".
• The repo has only one workflow file, so the update is complete; the PR description's mention of "across the workflows" reflects org-wide context rather than multiple files in this repo.

Confidence Score: 5/5

Safe to merge — the change is a single-line version pin with no logic, permission, or secret-handling implications.

The diff touches exactly one line in one file, replacing a pinned Dagger CLI version with the next patch release. Both jobs in the workflow remain structurally identical, and no secrets, permissions, or module references were altered.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/pr.yaml	Single-line DAGGER_VERSION bump from 0.20.6 to 0.20.8; no logic changes, no other workflow files in this repo.

_{Reviews (1): Last reviewed commit: "🔧 fix: bump DAGGER_VERSION 0.20.6 → 0.2..." | Re-trigger Greptile}