chore: installing pnpm instead of relying on cache

[Kylejeong2]

what

pnpm installation broke in release, this installs fresh instead of trying to access cached pnpm installation.

[greptile-apps]

Greptile Summary

This PR fixes a GitHub Actions workflow issue in the release pipeline by modifying the package manager setup order and caching strategy. The change moves the pnpm installation step to occur before Node.js setup and removes the cache: pnpm configuration from the setup-node action.

Specifically, the PR reorders the workflow steps so that pnpm/action-setup@v4 runs first (lines 19-22), followed by actions/setup-node@v4 (lines 24-27). The Node.js setup step no longer includes the cache: pnpm option, switching from a cached pnpm installation to a fresh installation approach.

This change addresses a common CI/CD issue where cached package manager installations become unreliable or inaccessible, causing release workflows to fail. By installing pnpm fresh on each workflow run, the pipeline becomes more self-contained and reliable. The reordering ensures that pnpm is available when the Node.js setup action needs it, following a standard pattern for GitHub Actions workflows that use pnpm.

Confidence score: 5/5

• This PR is safe to merge with minimal risk
• Score reflects a simple, well-understood CI/CD fix that addresses a specific infrastructure issue
• No files require special attention

Context used:

Context - We enforce linting and prettier at the CI level, so no code style comments that aren't obvious. (link)

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}