Closed depfu[bot] closed 4 years ago
Best reviewed: commit by commit
Powered by Pull Assistant. Last update f1d1ecb ... f1d1ecb. Read the comment docs.
1 updated dependency for you to review.
npm - a package manager for JavaScript
NPM | GitHub Repo | Homepage
Latest Version: 6.14.5 | Project Version: ^6.10.3 -> 6.14.5
We've tested your project with an updated dependency and the build failed.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of npm for this test run.
What changed?
✳️ npm (^6.10.3 → 6.14.5) · Repo · Changelog
Release Notes
6.14.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
6.14.5
update AUTHORS
chore: remove slack notification
docs: updated node-gyp links
chore: remove pyc files from tarball
chore: reenable windows ci
docs: changelog for 6.14.5
nopt@4.0.3
mkdirp@0.5.5
graceful-fs@4.2.4
npm-registry-fetch@4.0.4
npm init help wrong command
docs: fix minor typos in CONTRIBUTING.md
chore(docs): Fixed example typo & code style in npm-scripts.md
fix: relativize file links when inflating shrinkwrap
chore: avoid publish vim session file
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