chore(deps): bump webpack-dev-middleware from 5.3.1 to 5.3.4 in /docs #1418
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) from 5.3.1 to 5.3.4. - [Release notes](https://github.com/webpack/webpack-dev-middleware/releases) - [Changelog](https://github.com/webpack/webpack-dev-middleware/blob/v5.3.4/CHANGELOG.md) - [Commits](webpack/webpack-dev-middleware@v5.3.1...v5.3.4) --- updated-dependencies: - dependency-name: webpack-dev-middleware dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
D0 - Dependencies
There was a problem hiding this comment.
This update looks safe since releases : 5.3.1, 5.3.2, 5.3.3, 5.3.4 have only bug fixes and feat.
However, the versioning in the releases does not look very conventional. It goes from 5.3.3 to v6.0.0 up until v7.1.0 and then again there is a v5.3.4 release. It's as if they are simultaneously maintaining two ongoing streams of versions.
Yea this is normal for security updates. Especially for popular packages. |
Imod7
deleted the
dependabot/npm_and_yarn/docs/webpack-dev-middleware-5.3.4
branch
Bumps webpack-dev-middleware from 5.3.1 to 5.3.4.
Release notes
Sourced from webpack-dev-middleware's releases.
Changelog
Sourced from webpack-dev-middleware's changelog.
Commits
86071eachore(release): 5.3.4189c4acfix(security): do not allow to read files above (#1779)f3c62b8chore(release): 5.3.3eeb8aa8fix: types forRequestandResponse(#1271)1a45388chore(release): 5.3.2b8fb945chore(deps): memfs force update (#1269)f88067dchore: update deps and ci (#1260)7186318chore(deps-dev): bump@commitlint/cli57c50efci: updatecheckout,setup-node, andcodecovactions (#1267)840146achore(deps-dev): bump@babel/preset-envDependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)You can disable automated security fix PRs for this repo from the Security Alerts page.