mirror of
https://github.com/lipis/flag-icons.git
synced 2026-04-26 09:25:50 +03:00
[PR #738] [MERGED] [Security] Bump lodash from 4.17.14 to 4.17.19 #983
Labels
No labels
3rd-party
3rd-party
bug
code
documentation
enhancement
fixed-in-master
flag-request
help needed
missing-flag
missing-flag
pull-request
wrong-flag
wrong-flag
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/flag-icons#983
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/lipis/flag-icons/pull/738
Author: @dependabot-preview[bot]
Created: 7/16/2020
Status: ✅ Merged
Merged: 7/16/2020
Merged by: @dependabot-preview[bot]
Base:
master← Head:dependabot/npm_and_yarn/lodash-4.17.19📝 Commits (1)
fbc6185[Security] Bump lodash from 4.17.14 to 4.17.19📊 Changes
1 file changed (+3 additions, -3 deletions)
View changed files
📝
yarn.lock(+3 -3)📄 Description
Bumps lodash from 4.17.14 to 4.17.19. This update includes a security fix.
Vulnerabilities fixed
Sourced from The GitHub Security Advisory Database.
Release notes
Sourced from lodash's releases.
Commits
d7fbc52Bump to v4.17.192e1c0f2Add npm-package1b6c282Bump to v4.17.18a370ac8Bump to v4.17.171144918Rebuild lodash and docs3a3b0fdBump to v4.17.16c84fe82fix(zipObjectDeep): prototype pollution (#4759)e7b28eaSanitize sourceURL so it cannot affect evaled code (#4518)0cec225Fix lodash.isEqual for circular references (#4320) (#4515)94c3a81Document matches* shorthands for over* methods (#4510) (#4514)Maintainer changes
This version was pushed to npm by mathias, a new releaser for lodash since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.If all status checks pass Dependabot will automatically merge this pull request.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.