rm pnpm version specifier from CI

[seanmcguire12]

why

what changed

test plan

[changeset-bot]

⚠️ No Changeset found

Latest commit: 35b5d1e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[greptile-apps]

Greptile Summary

• Removed hardcoded version: 9 from pnpm action setup across 6 evaluation jobs (combination, act, extract, observe, targeted-extract, agent)
• pnpm version now automatically read from packageManager field in package.json (9.15.0), establishing single source of truth

Confidence Score: 5/5

• This PR is safe to merge with no risk
• Simple refactor that improves maintainability by using the existing packageManager field instead of duplicating version info, aligns with pnpm/action-setup@v4 best practices
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/ci.yml	Removed explicit pnpm version from 6 eval jobs, now using packageManager field from package.json as single source of truth

Sequence Diagram

sequenceDiagram
    participant CI as "GitHub Actions CI"
    participant Setup as "pnpm/action-setup@v4"
    participant PkgJSON as "package.json"
    CI->>Setup: "Setup pnpm"
    Setup->>PkgJSON: "Read packageManager field"
    PkgJSON-->>Setup: "pnpm@9.15.0"
    Setup-->>CI: "Install pnpm 9.15.0"

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile
React with 👍 or 👎 to share your feedback on this new summary format}