Skip to content
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

🚨 [security] [userscripts] Update webpack 5.39.1 → 5.91.0 (minor) #52

Open
wants to merge 1 commit into
base: osx
Choose a base branch
from
Open

🚨 [security] [userscripts] Update webpack 5.39.1 → 5.91.0 (minor) #52

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Mar 21, 2024

🚨 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 update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ webpack (5.39.1 → 5.91.0) · Repo

Security Advisories 🚨

🚨 Cross-realm object access in Webpack 5

Webpack 5 before 5.76.0 does not avoid cross-realm object access. ImportParserPlugin.js mishandles the magic comment feature. An attacker who controls a property of an untrusted object can obtain access to the real global object.

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.

↗️ @​types/eslint (indirect, 7.2.13 → 8.56.6) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ @​types/estree (indirect, 0.0.47 → 1.0.5) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ @​types/json-schema (indirect, 7.0.7 → 7.0.15) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ acorn (indirect, 8.4.0 → 8.11.3) · Repo

Commits

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

↗️ browserslist (indirect, 4.16.6 → 4.23.0) · Repo · Changelog

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.

↗️ caniuse-lite (indirect, 1.0.30001238 → 1.0.30001599) · Repo · Changelog

↗️ electron-to-chromium (indirect, 1.3.752 → 1.4.714) · Repo · Changelog

Commits

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

↗️ es-module-lexer (indirect, 0.4.1 → 1.4.2) · Repo · Changelog

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.

↗️ escalade (indirect, 3.1.1 → 3.1.2) · Repo

Release Notes

3.1.2

Patches

Chores

Full Changelog: v3.1.1...v3.1.2

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

Commits

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

↗️ graceful-fs (indirect, 4.2.6 → 4.2.11) · Repo

Commits

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

↗️ jest-worker (indirect, 27.0.2 → 27.5.1) · Repo · Changelog

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.

↗️ node-releases (indirect, 1.1.73 → 2.0.14) · Repo

Commits

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

↗️ punycode (indirect, 2.1.1 → 2.3.1) · Repo

Commits

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

↗️ schema-utils (indirect, 3.0.0 → 3.3.0) · Repo · Changelog

Commits

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

↗️ serialize-javascript (indirect, 5.0.1 → 6.0.2) · Repo

Release Notes

6.0.2

v6.0.1...v6.0.2

6.0.1

What's Changed

New Contributors

Full Changelog: v6.0.0...v6.0.1

6.0.0

Changelog

  • Add support for URL's (#123)
  • Bump mocha from 9.0.0 to 9.0.1 (#124)
  • Bump mocha from 8.4.0 to 9.0.0 (#121)
  • Update Node.js CI matrix (#122)
  • Bump mocha from 8.3.2 to 8.4.0 (#120)
  • Bump lodash from 4.17.19 to 4.17.21 (#119)
  • Bump y18n from 4.0.0 to 4.0.1 (#116)
  • Bump chai from 4.3.3 to 4.3.4 (#115)
  • Bump mocha from 8.3.1 to 8.3.2 (#114)
  • Bump mocha from 8.3.0 to 8.3.1 (#113)
  • Bump chai from 4.3.1 to 4.3.3 (#112)
  • Bump chai from 4.2.0 to 4.3.1 (#111)
  • Bump mocha from 8.2.1 to 8.3.0 (#109)
  • Bump mocha from 8.1.3 to 8.2.1 (#105)
  • Drop Travis CI settings (#100)
  • Change default branch name to main (#99)
  • GitHub Aactions (#98)

Behavior changes for URL objects

It serializes URL objects as follows since this version. The result of serialization may be changed if you are passing URL object values into the serialize-javascript.

const serialize = require("serialize-javascript");

serialize({u: new URL("http://example.com/")}); // '{"u":new URL("http://example.com/")}'

Thank you @rrdelaney for this release.

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

Commits

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

↗️ source-map-support (indirect, 0.5.19 → 0.5.21) · Repo

Commits

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

↗️ terser (indirect, 5.7.0 → 5.29.2) · Repo · Changelog

Security Advisories 🚨

🚨 Terser insecure use of regular expressions before v4.8.1 and v5.14.2 leads to ReDoS

The package terser before 4.8.1, from 5.0.0 and before 5.14.2 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regular expressions.

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.

↗️ terser-webpack-plugin (indirect, 5.1.3 → 5.3.10) · Repo · Changelog

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.

↗️ watchpack (indirect, 2.2.0 → 2.4.1) · Repo

Release Notes

2.4.1

Bugfixes

  • do not report directory as initial missing on the second watch

2.4.0

Bugfixes

  • respect filesystem accuracy more accurately

2.3.0

Features

  • allow to grab separate file and directory time info objects
  • allow functions passed to the ignored option

Bugfixes

  • ignore EACCESS errors during initial scan

Performance

  • improve performance of watcher update

Contributing

  • CI tests node.js 17 too

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

Commits

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

↗️ webpack-sources (indirect, 2.3.0 → 3.2.3) · Repo

Release Notes

3.2.2

Bugfixes

  • Source Code is splitted into lines via custom code instead of using a RegExp
    • In weird edge cases the RegExp caused a Stack Overflow

3.2.1

Bugfixes

  • RawSources with Buffers can now be concatenated with ConcatSource
  • Source Code is splitted into lines via custom code instead of using a RegExp
    • In weird edge cases the RegExp caused a Stack Overflow

3.2.0

Performance

  • add SourceMapSource.buffer for better performance
  • more efficient serialization of source mappings

Bugfix

  • avoid crashing when trying to compare the name with the original source, but there is no sourcesContent in SourceMap

3.1.2

Bugfix

  • improve handling of invalid mappings (like zero sized or negative)

3.0.4

Bugfix

  • fix invalid mappings when multiple lines with multiple chunks are replaced

3.0.2

Bugfix

  • fix incorrect offset sign when doing replacements

3.0.1

Bugfixes

  • fix ConcatSource off-by-1 bug

3.0.0

Performance

  • remove all dependencies
  • refactoring for performance
    • remove node() and listMap()
    • add streamChunks()

2.3.1

Performance

  • fix type bug in CachedSource which lead to bad hashing performance

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

Commits

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

🆕 @​jridgewell/gen-mapping (added, 0.3.5)

🆕 @​jridgewell/resolve-uri (added, 3.1.2)

🆕 @​jridgewell/set-array (added, 1.2.1)

🆕 @​jridgewell/source-map (added, 0.3.6)

🆕 @​jridgewell/sourcemap-codec (added, 1.4.15)

🆕 @​jridgewell/trace-mapping (added, 0.3.25)

🆕 acorn-import-assertions (added, 1.9.0)

🆕 json-parse-even-better-errors (added, 2.3.1)

🆕 picocolors (added, 1.0.0)

🆕 update-browserslist-db (added, 1.0.13)

🗑️ colorette (removed)

🗑️ json-parse-better-errors (removed)

🗑️ source-list-map (removed)

🗑️ yocto-queue (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 Mar 21, 2024
@depfu depfu bot mentioned this pull request Mar 21, 2024
Closed
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.

None yet
0 participants