🚨 [security] Update grunt: 1.4.1 → 1.6.0 (minor) #227
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ grunt (1.4.1 → 1.6.0) · Repo · Changelog
Security Advisories 🚨
🚨 Race Condition in Grunt
🚨 Path Traversal in Grunt
Release Notes
1.6.0
1.5.3
1.5.2
1.5.1
1.5.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 27 commits:
1.6.0
Merge pull request #1750 from gruntjs/dep-update-jan28
README updates
Bump to 16
Update more deps
Bump eslint and node version
1.5.3
Merge pull request #1745 from gruntjs/fix-copy-op
Patch up race condition in symlink copying.
Merge pull request #1746 from JamieSlome/patch-1
Create SECURITY.md
1.5.2
Update Changelog
Merge pull request #1743 from gruntjs/cleanup-link
Clean up link handling
1.5.1
Merge pull request #1742 from gruntjs/update-symlink-test
Fix symlink test
1.5.0
Updated changelog
Merge pull request #1740 from gruntjs/update-deps-22-10
Update testing matrix
More updates
Remove console log
Update dependencies, tests...
Merge pull request #1736 from justlep/main
support .cjs extension
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/
.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