build(deps): Bump sharp and next - #59
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [sharp](https://github.com/lovell/sharp) to 0.35.4 and updates ancestor dependency [next](https://github.com/vercel/next.js). These dependencies need to be updated together. Updates `sharp` from 0.34.5 to 0.35.4 - [Release notes](https://github.com/lovell/sharp/releases) - [Commits](lovell/sharp@v0.34.5...v0.35.4) Updates `next` from 16.2.12 to 16.3.4 - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.2.12...v16.3.4) --- updated-dependencies: - dependency-name: sharp dependency-version: 0.35.4 dependency-type: indirect - dependency-name: next dependency-version: 16.3.4 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
added
dependencies
This was referenced Sep 2, 2026
miaulalala
added a commit
that referenced
this pull request
Sep 2, 2026
* ci: verify pull requests before they reach main Nothing checked pull requests. The only workflow was the Pages deploy, which runs on push to main, so a change that broke the build was found either by the deploy failing or by the live site changing. On the four open Dependabot PRs the sole check is DCO. That matters most for the dependency bumps: #50 and #59 move Next from 16.2.12 to 16.3.x and sharp from 0.34 to 0.35, and AGENTS.md already warns that this Next.js has breaking changes between versions. Merging those with nothing having built the site is how a broken bump reaches the live course. Runs lint, tsc --noEmit, and the production build, on Node 24 to match the deploy workflow so a PR cannot pass here and fail there. The build is the load-bearing step: this is a static export, so it renders every route, and a missing generateStaticParams or a manifest entry pointing at nothing fails here instead of in production. This is also the prerequisite for auto-approving Dependabot: without a build check, auto-merge would land bumps unverified. AI-Assisted-By: Claude Opus 5 (1M context) Signed-off-by: Anna Larch <[email protected]> * ci: make the lint step advisory until main is clean The workflow failed on its own pull request, which is the useful kind of failure: main already has three react-hooks/set-state-in-effect errors, in CatalogClient, LevelCatalogClient and ModulePlayerClient. All three are the same pattern - reading saved progress from localStorage on mount - and that effect is deliberate. localStorage does not exist during prerender, and a lazy useState initialiser would make the prerendered HTML differ from the client render and mismatch on hydration. Satisfying the rule honestly means moving to useSyncExternalStore in three components, which is a separate change with its own risk to progress behaviour. So lint runs but does not block. A required check that main itself fails would make every pull request red and teach everyone to ignore CI, which is worse than not having the check. tsc and the build stay blocking - those are the ones that catch a broken dependency bump, which is what this workflow is for. AI-Assisted-By: Claude Opus 5 (1M context) Signed-off-by: Anna Larch <[email protected]> --------- Signed-off-by: Anna Larch <[email protected]>
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 to 0.35.4 and updates ancestor dependency next. These dependencies need to be updated together.
Updates
sharpfrom 0.34.5 to 0.35.4Release 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)Updates
nextfrom 16.2.12 to 16.3.4Release notes
Sourced from next's releases.
... (truncated)
Commits
299180dv16.3.412e173d[16.3.x] Re-enable AVIF image optimization and require sharp 0.35.4 (#97949)5d9022e[backport] Fix unset crossOrigin in Turbopack manifests (#97930)d8f4560[16.3.x] Fix build error when aliasing typescript to@typescript/typescript6...656aebf[16.3] testmode: Fix infinite recursion in testmode passthrough fetch (#97691)f37c1d6[16.3.x] ci: remove pull_request_stats workflow (#97975)a9a1cb7v16.3.3968b9fc[16.3.x] Fix ISR misses with backslashes in segments when deployed on Windows3a15b4a[16.3.x] [next/image]: disable avif image optimization7378b51Backport/docs fixes 16.3 (#97649)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.