Bump path-to-regexp and express #417
Conversation
|
There still seems to be an issue with pulldasher-dev. https://pulldasher-dev.cominor.com/auth/github/callback?code=9cefd23cb793d59c568d
These are both minor bumps on a dev-only repo. Unless there's good reason, we probably don't need to manually qa these. This fell off my radar: #416. Same there. I'm not sure if we need to be be manually testing pulldasher bump pulls unless there's a major change or a good reason. I don't know that manual qa on bump pulls in ifixit/pulldasher have ever come up with something. @davidrans thoughts? EDIT: Looks like we discussed disabling some perms for pulldasher-dev here: https://ifixit.slack.com/archives/C90126AN4/p1709235351576969?thread_ts=1709226588.477019&cid=C90126AN4 |
|
@dependabot rebase |
|
Fixed pulldasher-dev by updating the token. |
Bumps [path-to-regexp](https://github.com/pillarjs/path-to-regexp) to 0.1.12 and updates ancestor dependency [express](https://github.com/expressjs/express). These dependencies need to be updated together. Updates `path-to-regexp` from 0.1.10 to 0.1.12 - [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.10...v0.1.12) Updates `express` from 4.21.0 to 4.21.2 - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/4.21.2/History.md) - [Commits](expressjs/express@4.21.0...4.21.2) --- updated-dependencies: - dependency-name: path-to-regexp dependency-type: indirect - dependency-name: express dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/multi-6bc014718a
branch
from
60a06de to
a103d03
Compare
|
CR 📱 QA 📱 pulldasher-dev is working fine. |
4 participants
Bumps path-to-regexp to 0.1.12 and updates ancestor dependency express. These dependencies need to be updated together.
Updates
path-to-regexpfrom 0.1.10 to 0.1.12Release notes
Sourced from path-to-regexp's releases.
Commits
640e6940.1.12f01c26aMerge commit from fork0c711920.1.118f09549Add error on bad input valuesUpdates
expressfrom 4.21.0 to 4.21.2Release notes
Sourced from express's releases.
Changelog
Sourced from express's changelog.
Commits
1faf2284.21.22e0fb64deps: bump path-to-regexp@0.1.12 (#6209)59fc270deps: path-to-regexp@0.1.11 (#5956)51fc39cdocs: add funding (#6065)8e229f94.21.1a024c8afix(deps): cookie@0.7.1Maintainer changes
This version was pushed to npm by jonchurch, 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.