Skip to content

🚨 [security] Update gh-pages 3.2.3 → 6.1.1 (major)#93

Open
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/npm/gh-pages-6.1.1
Open

🚨 [security] Update gh-pages 3.2.3 → 6.1.1 (major)#93
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/npm/gh-pages-6.1.1

Conversation

@depfu
Copy link

@depfu depfu bot commented Apr 23, 2024

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

🚨 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?

✳️ gh-pages (3.2.3 → 6.1.1) · Repo · Changelog

Security Advisories 🚨

🚨 tschaub gh-pages vulnerable to prototype pollution

Prototype pollution vulnerability in tschaub gh-pages via the partial variable in util.js.

Release Notes

6.1.1

Fixes

  • fix: Add missing cname option not passed to the config by @WillBAnders in #535

Dependency Updates

New Contributors

Full Changelog: v6.1.0...v6.1.1

6.1.0

What's Changed

Full Changelog: v6.0.0...v6.1.0

6.0.0

This release drops support for Node 14. Otherwise, there are no special upgrade considerations.

What's Changed

New Contributors

Full Changelog: v5.0.0...v6.0.0

5.0.0

Potentially breaking change: the publish method now always returns a promise. Previously, it did not return a promise in some error cases. This should not impact most users.

Updates to the development dependencies required a minimum Node version of 14 for the tests. The library should still work on Node 12, but tests are no longer run in CI for version 12. A future major version of the library may drop support for version 12 altogether.

What's Changed

New Contributors

Full Changelog: v4.0.0...v5.0.0

4.0.0

This release doesn't include any breaking changes, but due to updated development dependencies, tests are no longer run on Node 10.

What's Changed

Full Changelog: v3.2.3...v4.0.0

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.

↗️ async (indirect, 2.6.4 → 3.2.5) · Repo · Changelog

Security Advisories 🚨

🚨 Prototype Pollution in async

A vulnerability exists in Async through 3.2.1 for 3.x and through 2.6.3 for 2.x (fixed in 3.2.2 and 2.6.4), which could let a malicious user obtain privileges via the mapValues() method.

Release Notes

3.2.4 (from changelog)

  • Fix a bug in priorityQueue where it didn't wait for the result. (#1725)
  • Fix a bug where unshiftAsync was included in priorityQueue. (#1790)

3.2.3 (from changelog)

  • Fix bugs in comment parsing in autoInject. (#1767, #1780)

3.2.2 (from changelog)

  • Fix potential prototype pollution exploit

3.2.1 (from changelog)

3.2.0 (from changelog)

  • Fix a bug in Safari related to overwriting func.name
  • Remove built-in browserify configuration (#1653)
  • Varios doc fixes (#1688, #1703, #1704)

3.1.1 (from changelog)

  • Allow redefining name property on wrapped functions.

3.1.0 (from changelog)

  • Added q.pushAsync and q.unshiftAsync, analagous to q.push and q.unshift, except they always do not accept a callback, and reject if processing the task errors. (#1659)
  • Promises returned from q.push and q.unshift when a callback is not passed now resolve even if an error ocurred. (#1659)
  • Fixed a parsing bug in autoInject with complicated function bodies (#1663)
  • Added ES6+ configuration for Browserify bundlers (#1653)
  • Various doc fixes (#1664, #1658, #1665, #1652)

3.0.1 (from changelog)

Bug fixes

  • Fixed a regression where arrays passed to queue and cargo would be completely flattened. (#1645)
  • Clarified Async's browser support (#1643)

3.0.0 (from changelog)

The async/await release!

There are a lot of new features and subtle breaking changes in this major version, but the biggest feature is that most Async methods return a Promise if you omit the callback, meaning you can await them from within an async function.

const results = await async.mapLimit(urls, 5, async url => {
    const resp = await fetch(url)
    return resp.body
})

Breaking Changes

  • Most Async methods return a Promise when the final callback is omitted, making them await-able! (#1572)
  • We are now making heavy use of ES2015 features, this means we have dropped out-of-the-box support for Node 4 and earlier, and many old versions of browsers. (#1541, #1553)
  • In queue, priorityQueue, cargo and cargoQueue, the "event"-style methods, like q.drain and q.saturated are now methods that register a callback, rather than properties you assign a callback to. They are now of the form q.drain(callback). If you do not pass a callback a Promise will be returned for the next occurrence of the event, making them await-able, e.g. await q.drain(). (#1586, #1641)
  • Calling callback(false) will cancel an async method, preventing further iteration and callback calls. This is useful for preventing memory leaks when you break out of an async flow by calling an outer callback. (#1064, #1542)
  • during and doDuring have been removed, and instead whilst, doWhilst, until and doUntil now have asynchronous test functions. (#850, #1557)
  • limits of less than 1 now cause an error to be thrown in queues and collection methods. (#1249, #1552)
  • memoize no longer memoizes errors (#1465, #1466)
  • applyEach/applyEachSeries have a simpler interface, to make them more easily type-able. It always returns a function that takes in a single callback argument. If that callback is omitted, a promise is returned, making it awaitable. (#1228, #1640)

New Features

  • Async generators are now supported in all the Collection methods. (#1560)
  • Added cargoQueue, a queue with both concurrency and payload size parameters. (#1567)
  • Queue objects returned from queue now have a Symbol.iterator method, meaning they can be iterated over to inspect the current list of items in the queue. (#1459, #1556)
  • A ESM-flavored async.mjs is included in the async package. This is described in the package.json "module" field, meaning it should be automatically used by Webpack and other compatible bundlers.

Bug fixes

  • Better handle arbitrary error objects in asyncify (#1568, #1569)

Other

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.

↗️ email-addresses (indirect, 3.1.0 → 5.0.0) · Repo · Changelog

Release Notes

5.0.0 (from changelog)

Note: Again there is a major version bump because of changes to the typescript definitions. If you are not a typescript user, this is more like a minor version bump.

  • Added "addressListSeperator" option (#57)
  • Typescript: improvements to the type definitions (#58, #59)

4.0.0 (from changelog)

Note: Again there is a major version bump because of changes to the typescript definitions. Some of the typescript changes are really bug fixes, noting where null is a possible value. If you are not a typescript user, this is more like a minor version bump.

  • Added "commaInDisplayName" option (#54)
  • Typescript: improvements to the type definitions (#44, #45, #47)

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

Commits

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

↗️ jsonfile (indirect, 4.0.0 → 6.1.0) · Repo · Changelog

Release Notes

6.1.0 (from changelog)

  • Add finalEOL option to disable writing final EOL (#115, #137)
  • Update dependency (#138)

6.0.1 (from changelog)

  • Update dependency (#130)
  • Fix code style (#129)

6.0.0 (from changelog)

  • BREAKING: Drop support for Node 6 & 8 (#128)
  • BREAKING: Do not allow passing null as options to readFile() or writeFile() (#128)
  • Refactor internals (#128)

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

Commits

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

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 Apr 23, 2024
@netlify
Copy link

netlify bot commented Apr 23, 2024 •
edited
Loading

✅ Deploy Preview for remarkable-entremet-e59b41 ready!

Name Link
🔨 Latest commit 02c2957
🔍 Latest deploy log https://app.netlify.com/sites/remarkable-entremet-e59b41/deploys/6626fbaad4c11f00088160bd
😎 Deploy Preview https://deploy-preview-93--remarkable-entremet-e59b41.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

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