next.js
be6e4bf4 - Upgrade sharp dependency to version ^0.34.4 (#83892)

Commit
167 days ago
Upgrade sharp dependency to version ^0.34.4 (#83892) ## ✅ Sharp Dependency Upgrade to Version ^0.34.4 - LOCKFILE FIXED ### Task Summary: Successfully upgraded the `sharp` dependency from version `^0.34.3` to `^0.34.4` and **fixed the pnpm lockfile issue** by running `pnpm install` to update the lockfile. ### ✅ Completed Steps: - [x] Explore repository structure and understand current sharp dependency (^0.34.3 in packages/next/package.json) - [x] Verify pnpm and corepack availability - [x] Enable pnpm using corepack in the repository - [x] Navigate to packages/next directory - [x] Update sharp dependency from ^0.34.3 to ^0.34.4 using pnpm add sharp@0.34.4 (manual edit after pnpm command) - [x] Update sharp dependency in test/integration/sharp-api/app/package.json for consistency - [x] **FIX: Run `pnpm install --no-frozen-lockfile` to properly update pnpm-lock.yaml** - [x] **Apply caret range ^0.34.4 instead of exact version per maintainer feedback** - [x] Validate JSON syntax of all modified package.json files - [x] Verify version numbers are correctly updated - [x] Run comprehensive verification tests - [x] Final verification and cleanup completed ### 📝 Changes Made: 1. **packages/next/package.json**: Updated `"sharp": "^0.34.3"` to `"sharp": "^0.34.4"` in optionalDependencies (caret range to allow patch updates) 2. **test/integration/sharp-api/app/package.json**: Updated `"sharp": "^0.34.3"` to `"sharp": "^0.34.4"` in dependencies (caret range for test compatibility) 3. **pnpm-lock.yaml**: **FIXED** - Properly updated with `pnpm install` to include sharp@0.34.4 and new `@img/colour` dependency ### ✅ Lockfile Fix Verification: - ✅ Sharp@0.34.4 now properly referenced 2 times in pnpm-lock.yaml - ✅ No remaining sharp@0.34.3 references in lockfile - ✅ New `@img/colour@1.0.0` dependency included (replacing old `color` package as noted by @styfle) - ✅ All platform-specific sharp binaries updated to 0.34.4 - ✅ Lockfile is now consistent with package.json changes - ✅ Caret range `^0.34.4` allows future patch updates while maintaining compatibility ### 🎯 Requirements Met: - ✅ Used `corepack enable pnpm` as requested - ✅ Attempted `pnpm add sharp@0.34.4` in ./packages/next directory as requested - ✅ **Fixed lockfile issue by running `pnpm install` as suggested by @styfle** - ✅ **Applied caret range ^0.34.4 instead of exact version per maintainer feedback** - ✅ Successfully upgraded to version 0.34.4 with proper semver range - ✅ Made minimal changes to only necessary files - ✅ Maintained existing code structure and functionality The upgrade is complete with the caret version range to allow future patch updates and the CI lockfile error should now be resolved! <!-- START COPILOT CODING AGENT SUFFIX --> <!-- START COPILOT CODING AGENT TIPS --> --- 💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Steven <steven@ceriously.com>
Author
Parents
Loading