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] Update gh-pages 2.2.0 → 6.1.1 (major) #217

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

🚨 [security] Update gh-pages 2.2.0 → 6.1.1 (major) #217

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Apr 23, 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 upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ gh-pages (2.2.0 → 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

3.2.3

3.2.2 (from changelog)

  • #396 - Revert "security(deps): bump filenamify-url to 2.1.1" (@tschaub)

3.2.1 (from changelog)

  • #393 - security(deps): bump filenamify-url to 2.1.1 (@AviVahl)

3.2.0 (from changelog)

This release updates a few development dependencies and adds a bit of documentation.

3.0.0

Breaking changes:

None really. But tests are no longer run on Node < 10. Development dependencies were updated to address security warnings, and this meant tests could no longer be run on Node 6 or 8. If you still use these Node versions, you may still be able to use this library, but be warned that tests are no longer run on these versions.

All changes:

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:

↗️ filenamify (indirect, 1.2.1 → 4.3.0) · Repo

Release Notes

4.3.0

  • Remove trailing periods for consistency on Windows (#23) 34da1ce

v4.2.0...v4.3.0

4.2.0

v4.1.0...v4.2.0

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

Commits

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

↗️ fs-extra (indirect, 8.1.0 → 11.2.0) · Repo · Changelog

Release Notes

11.2.0 (from changelog)

  • Copy directory contents in parallel for better performance (#1026)
  • Refactor internal code to use async/await (#1020)

11.1.1 (from changelog)

  • Preserve timestamps when moving files across devices (#992, #994)

11.1.0 (from changelog)

  • Re-add main field to package.json for better TypeScript compatibility (#979, #981)

11.0.0 (from changelog)

Breaking Changes

  • Don't allow requiring fs-extra/lib/SOMETHING (switched to exports) (#974)
  • Require Node v14.14+ (#968, #969)

New Features

  • Add fs-extra/esm for ESM named export support; see docs for details (#746, #974)
  • Add promise support for fs.readv() (#970)

Bugfixes

  • Don't stat filtered items in copy* (#965, #971)
  • Remove buggy stats check in copy (#918, #976)

10.1.0 (from changelog)

  • Warn if fs.realpath.native does not exist, instead of erroring (#953)
  • Allow explicitly passing undefined options to move() (#947, #955)
  • Use process.emitWarning instead of console.warn (#954)

10.0.1 (from changelog)

  • Add sideEffects: false to package.json (#941)

10.0.0 (from changelog)

Breaking changes

The following changes, although technically semver-major, will not affect the vast majority of users:

  • Ensure correct type when destination exists for ensureLink*()/ensureSymlink*() (#826, #786, #870)
  • Error when attempting to copy*() unknown file type (#880)
  • Remove undocumented options for remove*() (#882)

Improvements

  • Allow changing case of filenames with move*(), even on technically case-insensitive filesystems (#759, #801)
  • Use native fs.rm*() for remove*() in environments that support it (#882, #806)
  • Improve emptyDir() performance (#885)

Bugfixes

  • Ensure copy*()'s filter function is not called more than necessary (#883, #809)
  • Fix move*() raising EPERM error when moving a file to the root of a drive on Windows (#897, #819)

Miscellaneous changes

9.1.0 (from changelog)

  • Add promise support for fs.rm() (#841, #860)
  • Upgrade universalify for performance improvments (#825)

9.0.1 (from changelog)

  • Fix issue with ensureFile() when used with Jest on Windows (#804, #805)
  • Remove unneeded process.umask() call (#791)
  • Docs improvements (#753, #795, #797)

9.0.0 (from changelog)

Breaking changes

The following changes, allthough technically breaking, will not affect the vast majority of users:

  • outputJson now outputs objects as they were when the function was called, even if they are mutated later (#702, #768)
  • Cannot pass null as an options parameter to *Json* methods (#745, #768)

Improvements

  • Add promise shims for fs.writev & fs.opendir (#747)
  • Better errors for ensureFile (#696, #744)
  • Better file comparison for older Node versions (#694)

Miscellaneous changes

  • Peformance optimizations (#762, #764)
  • Add missing documentation for aliases (#758, #766)
  • Update universalify dependency (#767)

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.

↗️ 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:

↗️ universalify (indirect, 0.1.2 → 2.0.1) · Repo

Release Notes

2.0.1

  • Performance improvements (thanks @H4ad!)

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

Commits

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

🗑️ filenamify-url (removed)

🗑️ humanize-url (removed)

🗑️ is-plain-obj (removed)

🗑️ normalize-url (removed)

🗑️ query-string (removed)

🗑️ sort-keys (removed)

🗑️ strict-uri-encode (removed)

🗑️ strip-url-auth (removed)

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