Update sharp to the latest release

[HarshaNalluru]

Description

sharp is a little behind and can be updated.

Use case

A current sharp keeps image processing aligned with upstream binaries.

Proposed solution

Update sharp to the latest release, refresh the lockfiles, and verify the affected package. Contributing guide: https://github.com/usemoss/moss/blob/main/CONTRIBUTING.md

Alternatives considered

No response

[aanarakal]

Am working on this issue

[danit-niwattananan-personal]

Took a look at this one. sharp isn't a direct dependency in this repo — it doesn't appear in any of the 30 package.json files. It only shows up in four lockfiles at 0.34.5, in every case as an optional transitive dependency of next:

• apps/next-js/package-lock.json
• apps/moss-llamaindex/frontend/package-lock.json
• examples/voice-agents/insurance-adjuster/ui/package-lock.json
• apps/livekit-moss-vercel/agent-react/pnpm-lock.yaml

next declares sharp@^0.34.5, which resolves to >=0.34.5 <0.35.0, so the current latest (0.35.3) is outside the permitted range. next@16.2.12 still declares ^0.34.5, so bumping Next wouldn't pull it in either.

That means the only way to land 0.35.3 is an overrides/resolutions pin that overrides Next's declared compatibility range — probably a maintainer decision rather than a good-first-issue change. Happy to open that PR if you want it, otherwise this issue may want closing.

[samanyugoyal2010]

@aanarakal @danit-niwattananan-personal I have fixed this issue in PR #504 if you guys have any feedback feel free to leave it