Skip to content

🚨 [security] Update vite 4.1.0 → 7.1.5 (major) #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
depfu wants to merge 1 commit into
base: main
Choose a base branch
from
Open

🚨 [security] Update vite 4.1.0 → 7.1.5 (major) #10

depfu wants to merge 1 commit into from

Conversation

@depfu
Copy link

@depfu depfu bot commented Sep 9, 2025

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

↗️ fsevents (indirect, 2.3.2 → 2.3.3) · Repo

Release Notes

2.3.3

Released to npm as v2.3.3

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 7 commits:

↗️ nanoid (indirect, 3.3.4 → 3.3.11) · Repo · Changelog

Security Advisories 🚨

🚨 Predictable results in nanoid generation when given non-integer values

When nanoid is called with a fractional value, there were a number of undesirable effects:

  1. in browser and non-secure, the code infinite loops on while (size--)
  2. in node, the value of poolOffset becomes fractional, causing calls to nanoid to return zeroes until the pool is next filled
  3. if the first call in node is a fractional argument, the initial buffer allocation fails with an error

Version 3.3.8 and 5.0.9 are fixed.

Release Notes

3.3.11

  • Fixed React Native support.

3.3.8 (from changelog)

  • Fixed a way to break Nano ID by passing non-integer size (by @myndzi).

3.3.6 (from changelog)

  • Fixed package.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 21 commits:

↗️ picocolors (indirect, 1.0.0 → 1.1.1) · Repo · Changelog

Release Notes

1.1.1

What's new?

  • Moved TypeScript declarations to a d.ts file #82
  • Reworked color detection algorithm to properly work with empty strings in NO_COLOR and FORCE_COLOR env variables #87
  • Eliminated require() call to make the package compatible with some tools #87

1.1.0

What's new?

  • Added bright color variants #55

1.0.1

What's new?

  • Updated color detection mechanism to work properly on Vercel Edge Runtime #64
  • Remove use of recursion to avoid possible stack overflow for very long inputs #56

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 16 commits:

↗️ postcss (indirect, 8.4.21 → 8.5.6) · Repo · Changelog

Security Advisories 🚨

🚨 PostCSS line return parsing error

An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be \r discrepancies, as demonstrated by @font-face{ font:(\r/*);} in a rule.

This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ source-map-js (indirect, 1.0.2 → 1.2.1) · Repo · Changelog

Release Notes

1.2.1

1.2.0

Allow to pass options to SourceMapGenerator using SourceMapGenerator.fromSourceMap as second argument

var generator = sourceMap.SourceMapGenerator.fromSourceMap(new SourceMapConsumer(), {
  ignoreInvalidMapping: true,
});
  • Add generator options to fromSourceMap (#22) @ai

1.1.0

Add ignoreInvalidMapping option to SourceMapGenerator. If enabled, source-map-js will not throw an error on the incorrect previous source map. Instead, it will print warnings and ignore broken mappings.

var generator = new sourceMap.SourceMapGenerator({
  file: "my-generated-javascript-file.js",
  sourceRoot: "http://example.com/app/js/",
  ignoreInvalidMapping: true,
});
  • Do not throw an error since broken prev map is popular issue #20 (#20) @ai
  • Add ignoreInvalidMapping option (#21) @7rulnik

1.0.3

  • Use sourceContents when non-null, even if it's an empty string (#17) @bshepherdson

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 16 commits:

🆕 @​esbuild/aix-ppc64 (added, 0.25.9)

🆕 @​esbuild/netbsd-arm64 (added, 0.25.9)

🆕 @​esbuild/openbsd-arm64 (added, 0.25.9)

🆕 @​esbuild/openharmony-arm64 (added, 0.25.9)

🆕 @​rollup/rollup-android-arm-eabi (added, 4.50.1)

🆕 @​rollup/rollup-android-arm64 (added, 4.50.1)

🆕 @​rollup/rollup-darwin-arm64 (added, 4.50.1)

🆕 @​rollup/rollup-darwin-x64 (added, 4.50.1)

🆕 @​rollup/rollup-freebsd-arm64 (added, 4.50.1)

🆕 @​rollup/rollup-freebsd-x64 (added, 4.50.1)

🆕 @​rollup/rollup-linux-arm-gnueabihf (added, 4.50.1)

🆕 @​rollup/rollup-linux-arm-musleabihf (added, 4.50.1)

🆕 @​rollup/rollup-linux-arm64-gnu (added, 4.50.1)

🆕 @​rollup/rollup-linux-arm64-musl (added, 4.50.1)

🆕 @​rollup/rollup-linux-loongarch64-gnu (added, 4.50.1)

🆕 @​rollup/rollup-linux-ppc64-gnu (added, 4.50.1)

🆕 @​rollup/rollup-linux-riscv64-gnu (added, 4.50.1)

🆕 @​rollup/rollup-linux-riscv64-musl (added, 4.50.1)

🆕 @​rollup/rollup-linux-s390x-gnu (added, 4.50.1)

🆕 @​rollup/rollup-linux-x64-gnu (added, 4.50.1)

🆕 @​rollup/rollup-linux-x64-musl (added, 4.50.1)

🆕 @​rollup/rollup-openharmony-arm64 (added, 4.50.1)

🆕 @​rollup/rollup-win32-arm64-msvc (added, 4.50.1)

🆕 @​rollup/rollup-win32-ia32-msvc (added, 4.50.1)

🆕 @​rollup/rollup-win32-x64-msvc (added, 4.50.1)

🆕 @​types/estree (added, 1.0.8)

🆕 fdir (added, 6.5.0)

🆕 tinyglobby (added, 0.2.15)

🆕 @​esbuild/android-arm (added, 0.25.9)

🆕 @​esbuild/android-arm (added, 0.18.20)

🆕 @​esbuild/android-arm64 (added, 0.25.9)

🆕 @​esbuild/android-arm64 (added, 0.18.20)

🆕 @​esbuild/android-x64 (added, 0.25.9)

🆕 @​esbuild/android-x64 (added, 0.18.20)

🆕 @​esbuild/darwin-arm64 (added, 0.25.9)

🆕 @​esbuild/darwin-arm64 (added, 0.18.20)

🆕 @​esbuild/darwin-x64 (added, 0.25.9)

🆕 @​esbuild/darwin-x64 (added, 0.18.20)

🆕 @​esbuild/freebsd-arm64 (added, 0.25.9)

🆕 @​esbuild/freebsd-arm64 (added, 0.18.20)

🆕 @​esbuild/freebsd-x64 (added, 0.25.9)

🆕 @​esbuild/freebsd-x64 (added, 0.18.20)

🆕 @​esbuild/linux-arm (added, 0.25.9)

🆕 @​esbuild/linux-arm (added, 0.18.20)

🆕 @​esbuild/linux-arm64 (added, 0.25.9)

🆕 @​esbuild/linux-arm64 (added, 0.18.20)

🆕 @​esbuild/linux-ia32 (added, 0.25.9)

🆕 @​esbuild/linux-ia32 (added, 0.18.20)

🆕 @​esbuild/linux-loong64 (added, 0.25.9)

🆕 @​esbuild/linux-loong64 (added, 0.18.20)

🆕 @​esbuild/linux-mips64el (added, 0.25.9)

🆕 @​esbuild/linux-mips64el (added, 0.18.20)

🆕 @​esbuild/linux-ppc64 (added, 0.25.9)

🆕 @​esbuild/linux-ppc64 (added, 0.18.20)

🆕 @​esbuild/linux-riscv64 (added, 0.25.9)

🆕 @​esbuild/linux-riscv64 (added, 0.18.20)

🆕 @​esbuild/linux-s390x (added, 0.25.9)

🆕 @​esbuild/linux-s390x (added, 0.18.20)

🆕 @​esbuild/linux-x64 (added, 0.25.9)

🆕 @​esbuild/linux-x64 (added, 0.18.20)

🆕 @​esbuild/netbsd-x64 (added, 0.25.9)

🆕 @​esbuild/netbsd-x64 (added, 0.18.20)

🆕 @​esbuild/openbsd-x64 (added, 0.25.9)

🆕 @​esbuild/openbsd-x64 (added, 0.18.20)

🆕 @​esbuild/sunos-x64 (added, 0.25.9)

🆕 @​esbuild/sunos-x64 (added, 0.18.20)

🆕 @​esbuild/win32-arm64 (added, 0.25.9)

🆕 @​esbuild/win32-arm64 (added, 0.18.20)

🆕 @​esbuild/win32-ia32 (added, 0.25.9)

🆕 @​esbuild/win32-ia32 (added, 0.18.20)

🆕 @​esbuild/win32-x64 (added, 0.25.9)

🆕 @​esbuild/win32-x64 (added, 0.18.20)

🆕 esbuild (added, 0.25.9)

🆕 esbuild (added, 0.18.20)

🆕 picomatch (added, 4.0.3)

🆕 rollup (added, 4.50.1)

🆕 rollup (added, 3.29.5)

🆕 vite (added, 7.1.5)

🆕 vite (added, 4.5.14)

🗑️ @​esbuild/android-arm (removed)

🗑️ @​esbuild/android-arm64 (removed)

🗑️ @​esbuild/android-x64 (removed)

🗑️ @​esbuild/darwin-arm64 (removed)

🗑️ @​esbuild/darwin-x64 (removed)

🗑️ @​esbuild/freebsd-arm64 (removed)

🗑️ @​esbuild/freebsd-x64 (removed)

🗑️ @​esbuild/linux-arm (removed)

🗑️ @​esbuild/linux-arm64 (removed)

🗑️ @​esbuild/linux-ia32 (removed)

🗑️ @​esbuild/linux-loong64 (removed)

🗑️ @​esbuild/linux-mips64el (removed)

🗑️ @​esbuild/linux-ppc64 (removed)

🗑️ @​esbuild/linux-riscv64 (removed)

🗑️ @​esbuild/linux-s390x (removed)

🗑️ @​esbuild/linux-x64 (removed)

🗑️ @​esbuild/netbsd-x64 (removed)

🗑️ @​esbuild/openbsd-x64 (removed)

🗑️ @​esbuild/sunos-x64 (removed)

🗑️ @​esbuild/win32-arm64 (removed)

🗑️ @​esbuild/win32-ia32 (removed)

🗑️ @​esbuild/win32-x64 (removed)

🗑️ esbuild (removed)

🗑️ rollup (removed)

🗑️ vite (removed)

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants