chore(deps): bump path-to-regexp, express and @nestjs/platform-express #907
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps path-to-regexp to 3.3.0 and updates ancestor dependencies path-to-regexp, express and @nestjs/platform-express. These dependencies need to be updated together.
Updates
path-to-regexp
from 0.1.10 to 3.3.0Release notes
Sourced from path-to-regexp's releases.
Changelog
Sourced from path-to-regexp's changelog.
... (truncated)
Commits
2eb1293
3.3.0d31670a
Add backtrack protection to 3.x release (#321)6d2e8db
3.2.00e0dce9
Add nativematch
function to librarydd966ea
Fixvalidate: false
examples in READMEead0298
Changed coverage tool to nyc (#201)1aa2238
Bump node version testsf232e6d
3.1.0cb331c6
Update dev dependencies36344dc
RenamenoValidate
option tovalidate
Updates
express
from 4.21.1 to 4.21.2Release notes
Sourced from express's releases.
Changelog
Sourced from express's changelog.
Commits
1faf228
4.21.22e0fb64
deps: bump [email protected] (#6209)59fc270
deps: [email protected] (#5956)51fc39c
docs: add funding (#6065)Maintainer changes
This version was pushed to npm by jonchurch, a new releaser for express since your current version.
Updates
@nestjs/platform-express
from 10.4.6 to 10.4.15Release notes
Sourced from
@nestjs/platform-express
's releases.... (truncated)
Commits
d0fb875
chore(@nestjs
) publish v10.4.15 release1d457fe
chore(@nestjs
) publish v10.4.14 releasef4b242a
fix(deps): update dependency express to v4.21.21eba012
chore(@nestjs
) publish v10.4.13 releasecf8d27c
chore(@nestjs
) publish v10.4.12 release7db85ad
fix(deps): update dependency tslib to v2.8.1bedf1fa
chore(@nestjs
) publish v10.4.11 release5ebe4b9
chore(@nestjs
) publish v10.4.10 release416830c
chore(@nestjs
) publish v10.4.9 released35006a
chore: update readmesDependabot 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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will 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 version
will 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 dependency
will 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.