chore(deps-dev): bump sharp from 0.35.2 to 0.35.4 in /apps/www - #49
Open
dependabot[bot] wants to merge 2 commits into
Open
dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [sharp](https://github.com/lovell/sharp) from 0.35.2 to 0.35.4. - [Release notes](https://github.com/lovell/sharp/releases) - [Commits](lovell/sharp@v0.35.2...v0.35.4) --- updated-dependencies: - dependency-name: sharp dependency-version: 0.35.4 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
Dependabot bumped apps/www/package.json but didn't update the lockfile, so every CI job failed at "Install dependencies" with ERR_PNPM_OUTDATED_LOCKFILE. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016o746zzmP3iua4RXwDzsEN
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps sharp from 0.35.2 to 0.35.4.
Release notes
Sourced from sharp's releases.
... (truncated)
Commits
7f1a0a2Release v0.35.4f927818Upgrade to sharp-libvips v1.3.3e802092Prerelease v0.35.4-rc.0e13eb2fCI: Fix wasm32 build (#4589)a82a0b3Upgrade to libvips v8.18.68044fe4Bound resize dimensions to coordinate limit147f859Docs: changelog entries for #4578 #4584ee5bfb8Tests: use yauzl directly rather than via extract-zip wrapper7a77889Bump uraimo/run-on-arch-action from 3.1.0 to 3.2.0 (#4588)ea5bef2Improve support for input Streams finishing before output is requested (#4584)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Human/agent addendum: Dependabot's own diff (
apps/www/package.jsononly) leftpnpm-lock.yamlstale, failing every job atpnpm install --frozen-lockfilewithERR_PNPM_OUTDATED_LOCKFILE. Pushed commit 4fec9d1 to this branch to regenerate the lockfile with the repo's pinnedpnpm@9.15.9; verified viagit diff pnpm-lock.yamlthat only thesharp/@img/sharp-*entries changed, and confirmedpnpm install --frozen-lockfilenow succeeds. That push flipsgithub.actoraway fromdependabot[bot], which is what re-enables the Preflight Evidence gate below (seeci.yml's comment on that job) — filling it in for this small fix rather than leaving the lane red.CodSpeedis separately expected to fail — pre-existing dashboard misconfiguration unrelated to this change, tracked in #46.Agent Preflight (Required)
Classification
External References
Reviewed the
pnpm install --frozen-lockfilefailure output (ERR_PNPM_OUTDATED_LOCKFILE) and compared against sibling Dependabot PRs #50/#51, which synced their lockfiles correctly, to confirm this PR's lockfile was the outlier and the fix pattern (regenerate with the pinned pnpm version).Codebase Impact Analysis
Regenerated the workspace-root
pnpm-lock.yamlto matchapps/www/package.json'ssharp0.35.2 -> 0.35.4 bump (pnpm install --no-frozen-lockfilewithpnpm@9.15.9, matchingpackageManagerinpackage.json). Confirmed viagit diff pnpm-lock.yamlthat only thesharp/@img/sharp-*entries underapps/www's importer changed — no other workspace project's resolved versions moved. Re-ranpnpm install --frozen-lockfileto confirm all 14 workspace projects now install cleanly.Documentation & Specs
N/A: dependency lockfile sync only, no docs/spec changes needed.
Constitution & Risk Check
Low risk: mechanical lockfile regeneration to match a version bump Dependabot already proposed and that carries a high compatibility score; no application code changed. Verified the diff is scoped to sharp's own entries before pushing, so no unrelated dependency drift was introduced.