Bump express from 5.1.0 to 5.2.0 in /ReaAaS-N-backend - #9
Conversation
Bumps [express](https://github.com/expressjs/express) from 5.1.0 to 5.2.0. - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/master/History.md) - [Commits](expressjs/express@v5.1.0...v5.2.0) --- updated-dependencies: - dependency-name: express dependency-version: 5.2.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
- express ^5.1.0 -> ^5.2.0 in ReaAaS-N-backend/package.json Addresses body-parser DoS (Dependabot alert #12) and path-to-regexp DoS/ReDoS vulnerabilities (alerts #46, #48) pulled in via Express 5.2.0. - Remove ReaAaS-N-frontend/ReaAaS-N-backend/ (stale orphan copy). This directory was a relic from Phase 0 and was triggering false Dependabot PRs #8 and #11. It was never part of the active stack. Closes Dependabot PRs #7, #8, #9, #11
|
Closed: applied manually in commit 100d45b. This PR could not be auto-merged (merge conflict — backend package.json was restructured during Phase 10). The upgrade has been applied directly:
|
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
|
Closed: applied manually in commit 100d45b. This PR could not be auto-merged (merge conflict — backend package.json was restructured during Phase 10). The upgrade has been applied directly:
|
2 similar comments
|
Closed: applied manually in commit 100d45b. This PR could not be auto-merged (merge conflict — backend package.json was restructured during Phase 10). The upgrade has been applied directly:
|
|
Closed: applied manually in commit 100d45b. This PR could not be auto-merged (merge conflict — backend package.json was restructured during Phase 10). The upgrade has been applied directly:
|
1 participant
Bumps express from 5.1.0 to 5.2.0.
Release notes
Sourced from express's releases.
... (truncated)
Changelog
Sourced from express's changelog.
Commits
4007ad1Release: 5.2.0 (#6920)2f64f68sec: security patch for CVE-2024-51999ed0ba3fbuild(deps): bump actions/checkout from 5.0.0 to 6.0.0 (#6928)8eace46build(deps): bump github/codeql-action from 4.31.2 to 4.31.6 (#6929)30bae81build(deps): bump coverallsapp/github-action from 2.3.6 to 2.3.7 (#6930)758d435deps: body-parser@^2.2.1 (#6922)77bcd52docs: update emeritus triagers (#6890)f33caf1Nominate to@efekrsklfor triage team (#6888)54af593refactor: use cached slice in app.listen (#6897)2551a7ddocs: switch badges from badgen.net to shields.io (#6900)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 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.