amtrack / force-dev-tool

[DEPRECATED] Command line tool supporting the Force.com development lifecycle
MIT License
108 stars 37 forks source link

fix(deps): update dependency fs-extra to v6 #147

Closed renovate[bot] closed 6 years ago

renovate[bot] commented 6 years ago

This Pull Request updates dependency fs-extra from ^5.0.0 to ^6.0.0

Release Notes ### [`v6.0.1`](https://github.com/jprichardson/node-fs-extra/blob/master/CHANGELOG.md#​601--2018-05-09) [Compare Source](https://github.com/jprichardson/node-fs-extra/compare/6.0.0...6.0.1) - Fix `fs.promises` `ExperimentalWarning` on Node v10.1.0 ([#​578](`https://github.com/jprichardson/node-fs-extra/pull/578`)) --- ### [`v6.0.0`](https://github.com/jprichardson/node-fs-extra/blob/master/CHANGELOG.md#​600--2018-05-01) [Compare Source](https://github.com/jprichardson/node-fs-extra/compare/5.0.0...6.0.0) - Drop support for Node.js versions 4, 5, & 7 ([#​564](`https://github.com/jprichardson/node-fs-extra/pull/564`)) - Rewrite `move` to use `fs.rename` where possible ([#​549](`https://github.com/jprichardson/node-fs-extra/pull/549`)) - Don't convert relative paths to absolute paths for `filter` ([#​554](`https://github.com/jprichardson/node-fs-extra/pull/554`)) - `copy*`'s behavior when `preserveTimestamps` is `false` has been OS-dependent since 5.0.0, but that's now explicitly noted in the docs ([#​563](`https://github.com/jprichardson/node-fs-extra/pull/563`)) - Fix subdirectory detection for `copy*` & `move*` ([#​541](`https://github.com/jprichardson/node-fs-extra/pull/541`)) - Handle case-insensitive paths correctly in `copy*` ([#​568](`https://github.com/jprichardson/node-fs-extra/pull/568`)) ---

This PR has been generated by Renovate Bot.

renovate[bot] commented 6 years ago

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 6.x releases. However, if you upgrade to 6.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.