The version 0.8.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of shelljs.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv0.8.0
Closed issues:
Snyk vulnerability DB reporting command injection vulnerability in ShellJS #810
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 99.891% when pulling 7ef59d3301621ed5b5bc2673fcfbb2e82ed3dc40 on greenkeeper/shelljs-0.8.0 into 6c0bacf4edc803c842c6cc54595d20c25c5c975c on master.
Coverage remained the same at 99.891% when pulling 7ef59d3301621ed5b5bc2673fcfbb2e82ed3dc40 on greenkeeper/shelljs-0.8.0 into 6c0bacf4edc803c842c6cc54595d20c25c5c975c on master.
Coverage remained the same at 99.891% when pulling 7ef59d3301621ed5b5bc2673fcfbb2e82ed3dc40 on greenkeeper/shelljs-0.8.0 into 6c0bacf4edc803c842c6cc54595d20c25c5c975c on master.
Version 0.8.0 of shelljs was just published.
The version 0.8.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of shelljs.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v0.8.0Closed issues:
ls regular-file.txt
#732Merged pull requests:
-q
(quiet) option topush
,popd
,dirs
functions. #777 (alexreg)Commits
The new version differs by 36 commits.
ec0d60a
0.8.0
8f8119c
docs: announce plugin API (#812)
0b65d2a
chore: update CI to Node v9 (#811)
a2343d0
refactor: harden plugins against unknown options (#804)
64d5899
refactor(exec): remove paramsFile (#807)
8ab0a3a
chore: update nyc dependency (#805)
6189d7f
Remove codeFile parameter (#791)
8451fce
chore(eslint): use words instead of numbers (#797)
a187bd1
Provide an API to pass parameters which resemble options (#792)
b885590
Use execFileSync to launch child process (#790)
e9461dc
Add note to issue template about FAQ (#794)
90165ba
docs(changelog): updated by Nate Fischer [ci skip]
9e3f9ab
refactor(exec): move child process to source file (#786)
a7d6df5
Wrap fs.statSync and fs.lstatSync (#783)
7cbce88
Add a test for ls for a single file (#784)
There are 36 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: