Bump lodash from 4.17.15 to 4.17.19 #1505
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.17.15...4.17.19) Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
|
@ArthurHoaro I've pushed the shaarli:latest Docker image against a vulnerability scanner, and I can confirm this dependency is indeed listed as vulnerable. This is probably a build dependency, so it shouldn't mean Shaarli is vulnerable or anything but I'd prefer a "no vulnerability" scan result instead of 11 items :) See also #1512 and here is the full scan report for reference to other recommended version bumps:
|
|
Hi, yes there has been multiple reports from the Github bot. I can bump this one, but there is probably a few which are outdated and will need work toward the webpack builds. |
|
Also, what tool did you use to get these alerts? |
|
Yes, according to the report there are multiple outdated packages. I pushed the image to a self-hosted Harbor docker registry which has an internal vulnerability scanner called Trivy but it can also be used as a standalone CLI tool: |
Bumps lodash from 4.17.15 to 4.17.19.
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.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 languageYou can disable automated security fix PRs for this repo from the Security Alerts page.