Bump path-to-regexp and express in /example/e2e #226
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [path-to-regexp](https://github.com/pillarjs/path-to-regexp) and [express](https://github.com/expressjs/express). These dependencies needed to be updated together. Updates `path-to-regexp` from 0.1.7 to 0.1.10 - [Release notes](https://github.com/pillarjs/path-to-regexp/releases) - [Changelog](https://github.com/pillarjs/path-to-regexp/blob/master/History.md) - [Commits](pillarjs/path-to-regexp@v0.1.7...v0.1.10) Updates `express` from 4.17.1 to 4.21.0 - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/4.21.0/History.md) - [Commits](expressjs/express@4.17.1...4.21.0) --- updated-dependencies: - dependency-name: path-to-regexp dependency-type: indirect - dependency-name: express dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
It looks like you are reviewing a Dependabot upgrade PR! 🛠️ We aim to merge Dependabot PRs within the below timeframes. The objectives are based on the severity of the security vulnerability we are mitigating with the upgrade:
🎯 Target merge date for this PR: 26/09/2024 🎯 FAQ What if we aren’t vulnerable to this particular CVE? Do we still have to upgrade the package?It’s still a good idea to upgrade the package if we can. With new code patterns and paths being introduced every day, we have no guarantee that we won’t later make ourselves vulnerable. Keeping packages up to date as a matter of due course is also good hygiene.What if we’re not vulnerable and upgrading is going to be a lot of work?In these cases it’s a good idea to list out the steps you took to confirm we are not vulnerable in this PR. The PR can then be closed and the corresponding Dependabot Alert should be dismissed with the triage steps included as a comment. Please get in touch with Team Application Security via #ask-security before dismissing anyCRITICAL alerts.
This is a major version upgrade that requires substantial code refactoring. What should I do?If the upgrade requires substantial refactoring then it is possible that we will miss the objectives we have outlined above. In these cases, you should add thedependabot-refactor-required label to this PR and ping #ask-security for further advice.
|
|
Hello @intercom/team-messenger 👋 this PR fixes a security vulnerability (GHSA-9wv6-86v2-598j) in a repository you own - intercom/intercom-react-native. We have obligation to update our dependencies in a timely manner in order to keep our applications secure. Please take a look at the PR and merge it as soon as possible. |
|
@dependabot rebase |
|
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
EmmanuelIntercom
deleted the
dependabot/npm_and_yarn/example/e2e/multi-1d234c620e
branch
Bumps path-to-regexp and express. These dependencies needed to be updated together.
Updates
path-to-regexpfrom 0.1.7 to 0.1.10Release notes
Sourced from path-to-regexp's releases.
Commits
c827fce0.1.1029b96b4Add backtrack protection to parametersac4c234Update repo url (#314)bdb66350.1.9c4272e4Allow a non-lookahead regex (#312)51a19550.1.8114f62dAdd support for named matching groups (#301)Updates
expressfrom 4.17.1 to 4.21.0Release notes
Sourced from express's releases.
... (truncated)
Changelog
Sourced from express's changelog.
... (truncated)
Commits
7e562c64.21.01bcde96fix(deps): [email protected] (#5946)7d36477fix(deps): [email protected] (#5951)40d2d8ffix(deps): [email protected]77ada90Deprecate"back"magic string in redirects (#5935)21df4214.20.04c9ddc1feat: upgrade to [email protected]9ebe5d5feat: upgrade to [email protected] (#5928)ec4a01bfeat: upgrade to [email protected] (#5926)54271f6fix: don't render redirect values in anchor hrefMaintainer changes
This version was pushed to npm by wesleytodd, a new releaser for express 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 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.