🔧 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 .github/workflows/pr.yaml to resolve a CLI/module version handshake failure that was blocking dagger call from running in CI.

• Updates the single env-level DAGGER_VERSION variable consumed by both check-pr-title and check-linear-magic-word jobs via dagger/dagger-for-github@v8.2.0.

Confidence Score: 5/5

This PR is safe to merge — it is a one-line version bump in a single CI workflow with no logic changes.

The change is a straightforward version pin update for the Dagger CLI, matching what other org repos have already shipped. Both jobs in the workflow consume the same env variable, so the bump applies consistently. There is nothing to break in the workflow logic itself.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/pr.yaml	Single-line version bump of DAGGER_VERSION from 0.20.6 to 0.20.8; no structural or logic changes.

Sequence Diagram

sequenceDiagram
    participant GHA as GitHub Actions
    participant DFG as dagger-for-github@v8.2.0
    participant CLI as Dagger CLI v0.20.8
    participant DV as daggerverse/ghcontrib

    GHA->>DFG: Install Dagger (version: 0.20.8)
    DFG->>CLI: "Download & install"
    GHA->>CLI: dagger call -m ghcontrib check-pull-request
    CLI->>DV: Version handshake (0.20.8 ✓)
    DV-->>GHA: Result (pass/fail)

Loading

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