chore: update pnpm

[mcansh]

Signed-off-by: GitHub noreply@github.com

Summary by CodeRabbit

• Chores
  • Updated package manager to a newer version for improved compatibility and performance.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: b6b2a79

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

[coderabbitai]

Walkthrough

The packageManager field in package.json is updated to specify pnpm version 10.24.0 with a new SHA512 hash, upgrading from the previous 10.14.0 version. This change pins the exact package manager version and integrity hash for consistency across environments.

Changes

Cohort / File(s)	Summary
Package Manager Version Update package.json	packageManager field updated from pnpm@10.14.0+sha512.ad27a79... to pnpm@10.24.0+sha512.01ff8ae...

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single field update in one file with no logic or control flow changes
• Straightforward version bump with corresponding hash update

Poem

🐰 A package manager springs forth,
From ten-point-fourteen to twenty-four north,
The hash has changed, the version rings true,
Consistency reigns in all that we do!
hops away happily 🎉

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: update pnpm' clearly and concisely summarizes the main change: upgrading the pnpm package manager version in package.json.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch logan/pnpm-10.24.0

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

More templates

• basic-example-template
• playground
• react-router-example-template
• vite-remix

npm i https://pkg.pr.new/@mcansh/remix-fastify@600

commit: b6b2a79

[Copilot]

Pull request overview

This PR updates the pnpm package manager version from 10.14.0 to 10.24.0 in the repository's package.json file.

• Updates the packageManager field with the new pnpm version and its corresponding SHA-512 hash

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ec3f908 and b6b2a79.

📒 Files selected for processing (1)

• package.json (1 hunks)

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Fetch pnpm@10.24.0 metadata from npm registry
npm view pnpm@10.24.0 dist.integrity 2>/dev/null || echo "Registry query failed, trying alternative method"

Repository: mcansh/remix-fastify

Length of output: 159

---

🌐 Web query:

pnpm 10.24.0 release notes breaking changes

💡 Result:

No breaking changes were listed for pnpm v10.24.0 — the release contains adaptive network concurrency and several patch fixes (trustPolicy, ENOENT handling, self-update revert, auth-token parsing, etc.). [1][2]

Sources:
[1] pnpm blog — "pnpm 10.24" release notes.
[2] GitHub releases — pnpm v10.24.0.

---

Correct the SHA512 hash — it does not match the official npm registry.

The SHA512 hash in package.json does not match the hash for pnpm@10.24.0 from npm registry:

• package.json hash: sha512-01ff8ae71b4419903b65c60fb2dc9d34cf8bb6e06d03bde112ef38f7a34d6904c424ba66bea5cdcf12890230bf39f9580473140ed9c946fef328b6e5238a345a
• npm registry hash: sha512-Af+K5xtEGZA7ZcYPstydNM+LtuBtA73hEu8496NNaQTEJLpmvqXNzxKJAjC/OflYBHMUDtnJRv7zKLblI4o0Wg==

Update the hash to match the official registry value. While pnpm 10.24.0 is stable with no breaking changes, the hash mismatch compromises reproducibility and security verification.

🤖 Prompt for AI Agents

In package.json around line 51, the packageManager SHA512 hash for pnpm@10.24.0
is incorrect; replace the existing sha512-01ff8ae7...a345a value with the
official npm registry hash for pnpm@10.24.0:
sha512-Af+K5xtEGZA7ZcYPstydNM+LtuBtA73hEu8496NNaQTEJLpmvqXNzxKJAjC/OflYBHMUDtnJRv7zKLblI4o0Wg==
so the entry becomes pnpm@10.24.0+sha512.<official-hash> ensuring
reproducibility and signature verification.