Bump json5, loader-utils and @storybook/polymer in /storybook #47
Conversation
Bumps [json5](https://github.com/json5/json5) to 2.2.3 and updates ancestor dependencies [json5](https://github.com/json5/json5), [loader-utils](https://github.com/webpack/loader-utils) and [@storybook/polymer](https://github.com/storybookjs/storybook/tree/HEAD/app/polymer). These dependencies need to be updated together. Updates `json5` from 2.1.0 to 2.2.3 - [Release notes](https://github.com/json5/json5/releases) - [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md) - [Commits](json5/json5@v2.1.0...v2.2.3) Updates `loader-utils` from 1.1.0 to 1.4.2 - [Release notes](https://github.com/webpack/loader-utils/releases) - [Changelog](https://github.com/webpack/loader-utils/blob/v1.4.2/CHANGELOG.md) - [Commits](webpack/loader-utils@v1.1.0...v1.4.2) Updates `@storybook/polymer` from 4.0.7 to 5.3.21 - [Release notes](https://github.com/storybookjs/storybook/releases) - [Changelog](https://github.com/storybookjs/storybook/blob/v5.3.21/CHANGELOG.md) - [Commits](https://github.com/storybookjs/storybook/commits/v5.3.21/app/polymer) --- updated-dependencies: - dependency-name: json5 dependency-type: indirect - dependency-name: loader-utils dependency-type: indirect - dependency-name: "@storybook/polymer" dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
Socket Security Pull Request ReportDependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again. 📜 Install scriptsInstall scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.
😵💫 Bin script confusionThis package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack Consider removing one of the conflicting packages. Packages should only export bin scripts with their name
Pull request report summary
Bot CommandsTo ignore an alert, reply with a comment starting with
Powered by socket.dev |
Bumps json5 to 2.2.3 and updates ancestor dependencies json5, loader-utils and @storybook/polymer. These dependencies need to be updated together.
Updates
json5from 2.1.0 to 2.2.3Release notes
Sourced from json5's releases.
Changelog
Sourced from json5's changelog.
... (truncated)
Commits
c3a75242.2.394fd06ddocs: update CHANGELOG for v2.2.33b8cebfdocs(security): use GitHub security advisoriesf0fd9e1docs: publish a security policy6a91a05docs(template): bug -> bug report14f8cb12.2.210cc7cadocs: update CHANGELOG for v2.2.27774c10fix: add proto to objects and arraysedde30aReadme: slight tweak to intro97286f8Improve example in readmeUpdates
loader-utilsfrom 1.1.0 to 1.4.2Release notes
Sourced from loader-utils's releases.
... (truncated)
Changelog
Sourced from loader-utils's changelog.
... (truncated)
Commits
331ad50chore(release): 1.4.217cbf8ffix: ReDoS problem (#226)8f082b3chore(release): 1.4.14504e34fix: security problem (#220)d95b8b5chore(release): 1.4.0cd0e428feat: theresourceQueryis passed to theinterpolateNamemethod (#163)06d36cfchore(release): 1.3.0469eebafeat: support the[query]template for theinterpolatedNamemethod (#162)909c99dchore: funding.yml config and CI fix (#159)b5b74f0Set up CI with Azure PipelinesMaintainer changes
This version was pushed to npm by evilebottnawi, a new releaser for loader-utils since your current version.
Updates
@storybook/polymerfrom 4.0.7 to 5.3.21Changelog
Sourced from
@storybook/polymer's changelog.... (truncated)
Commits
a939e72v5.3.21e5cff07Update git head to 5.3.20966a826v5.3.20e26136fv5.3.19ff445dav5.3.1844e01ffv5.3.178cd6918Update version.ts to 5.3.165e5197ev5.3.16db0e79bv5.3.1591d9c0cv5.3.14Dependabot 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.