Skip to content

build(deps-dev): bump sharp from 0.34.5 to 0.35.5 - #198

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/sharp-0.35.5
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/sharp-0.35.5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 23, 2026

Copy link
Copy Markdown
Contributor

Bumps sharp from 0.34.5 to 0.35.5.

Release notes

Sourced from sharp's releases.

v0.35.5

https://github.com/lovell/sharp-libvips/releases/tag/v1.3.4

  • Add upper bounds check on length of linear and GIF delay arrays.

  • Improve error handing when WebAssembly fallback also fails. #4593 @​lazerg

  • TypeScript: Allow multi-frame options for JXL output. #4602 @​ramin-010

  • TypeScript: Remove non-existent named export. #4604

  • Increase accepted dimensions when extending an image. #4605

  • Improve gain map support for extract and rotate operations. #4606

  • Tests: Ensure composite tests pass on big endian platforms. #4609

v0.35.5-rc.1

https://github.com/lovell/sharp-libvips/releases/tag/v1.3.4-rc.1

  • Add upper bounds check on length of linear and GIF delay arrays.

  • Improve error handing when WebAssembly fallback also fails. #4593 @​lazerg

  • TypeScript: Allow multi-frame options for JXL output. #4602 @​ramin-010

  • TypeScript: Remove non-existent named export. #4604

  • Increase accepted dimensions when extending an image. #4605

  • Improve gain map support for extract operation. #4606

... (truncated)

Commits
  • 51a990f Release v0.35.5
  • 96de105 Upgrade to sharp-libvips v1.3.4
  • 3a61390 CI: Configure Dependabot with all package.json locations
  • 4940c50 Improve gain map support for rotate/flip/flop ops
  • 20654aa Prerelease v0.35.5-rc.1
  • ef4f934 CI: Upgrade to Ubuntu 26.04
  • 358df95 Upgrade to libvips v8.18.7
  • 49f4903 Improve gain map support for rotate-then-extract #4606
  • 0e2e55e Silence a couple of compiler/static analysis warnings
  • cef3b8c Improve gain map support for extract operation #4606
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

Bumps [sharp](https://github.com/lovell/sharp) from 0.34.5 to 0.35.5.
- [Release notes](https://github.com/lovell/sharp/releases)
- [Commits](lovell/sharp@v0.34.5...v0.35.5)

---
updated-dependencies:
- dependency-name: sharp
  dependency-version: 0.35.5
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 23, 2026
ooloth added a commit that referenced this pull request Nov 6, 2026
…#215)

## ✅ What

- Changes Dependabot so npm security fixes arrive in one grouped PR
instead of one PR per package, and so major version upgrades are
proposed as their own PRs instead of never
- Minor and patch updates still arrive together in one monthly catch-all
PR per ecosystem (npm and GitHub Actions), and releases still wait 7
days before Dependabot proposes them
- The npm security group takes every kind of update, majors included, so
a breaking fix sits in the same PR as the others rather than being split
off. GitHub Actions gets no security group, because Dependabot creates
no alerts for actions pinned to a SHA, so their fixes arrive as version
updates
- Packages that only work at matching versions arrive together, majors
included: `next` with `eslint-config-next`, `react` with `react-dom` and
their types, `tailwindcss` with `@tailwindcss/postcss`, `vitest` with
`@vitest/ui`, and the `upload-artifact` and `download-artifact` actions
- `@types/node` stops at major 25, the Node version in `.nvmrc`, so
types never describe APIs the runtime doesn't have
- npm can have up to 10 Dependabot PRs open at once and GitHub Actions
up to 5, instead of 1 each, which leaves room for majors beside the
groups
- Starting the Check workflow by hand on any branch now runs Build,
Metadata and Lighthouse there too, without deploying. That is how a
Dependabot PR gets checked before it merges, and `CLAUDE.md` now says so
- `npm run deploy:ci` now only looks for runs on `main` when it reports
the run it started, so a check running on another branch can't be
mistaken for the deploy

## 🤔 Why

- 18 Dependabot PRs are open right now, one for each package with a
security alert, because the existing group only covered regular version
updates
- Majors were ignored entirely, so packages like `@types/node` had
fallen five majors behind with nothing proposing an upgrade
- The security group can't be limited to minor and patch, because
Dependabot judges a security update by the package's newest release
rather than by the fix. `ws` 7.5.10 is fixed by a patch, but 8.x exists,
so it would have been split off on its own
- CI can't build Dependabot PRs on its own, because GitHub gives them
none of the repo's Actions secrets, and the build fetches content with
those secrets. A run you start yourself does get the secrets, so
`CLAUDE.md` says to check each release for signs of a compromised
publish first, then start that run, and merge only once it passes on the
commit being merged
- Dependabot only reads its config from `main`, so none of the new
grouping shows until this merges

## 👩‍🔬 How to validate

- [ ] `git fetch origin && git switch dependabot-security-groups`
- [ ] `npx --yes js-yaml .github/dependabot.yml`
- [ ] Expect the file to parse and print as JSON, with `artifacts` and
`actions` under `github-actions`, and `next`, `react`, `tailwind`,
`vitest`, `npm` and `npm-security` under `npm`
- [ ] Expect only `actions` and `npm` to list `"update-types": ["minor",
"patch"]`, and `npm-security` to have no `update-types`
- [ ] Expect the `npm` entry to have `"open-pull-requests-limit": 10`
and an `ignore` for `@types/node` versions `>=26`
- [ ] `gh workflow run ci.yml -R ooloth/michaeluloth.com --ref
dependabot-security-groups`
- [ ] `gh run list -R ooloth/michaeluloth.com --workflow ci.yml --branch
dependabot-security-groups --event workflow_dispatch --json
databaseId,headSha,status --limit 1`
- [ ] Expect a new run whose `headSha` is the branch's latest commit,
then open it with `gh run view <databaseId> -R ooloth/michaeluloth.com`
- [ ] Expect Build, Metadata and Lighthouse to run and pass, and Deploy
and Notify to show as skipped
- [ ] Open `CLAUDE.md` and expect the "Dependency Updates" section to
say to check each release, then start that run, before merging a
Dependabot PR

## 🔖 Related links

- ooloth/dotfiles#251
- After this merges, Dependabot's first grouped security PR should
replace the per-package ones (#190, #191, #193 to #198, #200 to #209,
#213 and #214). Any it leaves open will be closed by hand
@dependabot @github

dependabot Bot commented on behalf of github Nov 6, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #217.

@dependabot dependabot Bot closed this Nov 6, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/sharp-0.35.5 branch November 6, 2026 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants