chore(deps): bump sharp from 0.35.0 to 0.35.3 in the production group across 1 directory - #37
Conversation
📝 WalkthroughWalkthroughThe web application’s ChangesWeb dependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Bumps the production group with 1 update in the / directory: [sharp](https://github.com/lovell/sharp). Updates `sharp` from 0.35.0 to 0.35.3 - [Release notes](https://github.com/lovell/sharp/releases) - [Commits](lovell/sharp@v0.35.0...v0.35.3) --- updated-dependencies: - dependency-name: sharp dependency-version: 0.35.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: production ... Signed-off-by: dependabot[bot] <support@github.com>
ee3c21f to
86793e7
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/web/package.json`:
- Line 46: Regenerate pnpm-lock.yaml after updating the sharp dependency to
0.35.3, ensuring the sharp override, importer entry, and package resolution all
consistently reference 0.35.3 so frozen-lockfile installs match the manifest.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: b6ec968b-5ec3-4886-89d0-45071444894d
📒 Files selected for processing (1)
apps/web/package.json
| "react-dom": "19.2.8", | ||
| "recharts": "3.10.1", | ||
| "sharp": "0.35.0", | ||
| "sharp": "0.35.3", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== apps/web/package.json ==\n'
grep -n '"sharp"' -n apps/web/package.json || true
printf '\n== lockfile sharp references ==\n'
rg -n '"sharp"|sharp@|sharp:' pnpm-lock.yaml apps/web/package.json || true
printf '\n== nearby lockfile context ==\n'
rg -n -C 2 'sharp' pnpm-lock.yaml || trueRepository: jusso-dev/Muster
Length of output: 11755
Regenerate pnpm-lock.yaml for the Sharp bump. The lockfile still pins sharp to 0.35.0 in the override, importer entry, and package resolution, so frozen-lockfile installs can keep resolving the old version or fail against the updated manifest.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/web/package.json` at line 46, Regenerate pnpm-lock.yaml after updating
the sharp dependency to 0.35.3, ensuring the sharp override, importer entry, and
package resolution all consistently reference 0.35.3 so frozen-lockfile installs
match the manifest.
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the production group with 1 update in the / directory: sharp.
Updates
sharpfrom 0.35.0 to 0.35.3Release notes
Sourced from sharp's releases.
... (truncated)
Commits
1018449Release v0.35.3ba303a7Prerelease v0.35.3-rc.24f94fc5Upgrade to sharp-libvips v1.3.2c5e7a3fBump devDeps, fix Deno/Windows smoke tests9a8d002Docs: Add changelog entry and note about transferable #45208694db0TypeScript: Return more preciseBuffer\<ArrayBuffer>fromtoBuffer(#4520)e000d0bPrerelease v0.35.3-rc.19554ca9Prerelease v0.35.3-rc.06a29fd5Emit warning about native binaries on Linux Electron540d2eaIncrease default concurrency when use of MALLOC_ARENA_MAX detectedSummary by CodeRabbit