deps(example): bump the dependencies group in /examples/nestjs with 2 updates #2878
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the dependencies group in /examples/nestjs with 2 updates: [@nestjs/core](https://github.com/nestjs/nest/tree/HEAD/packages/core) and [@nestjs/platform-express](https://github.com/nestjs/nest/tree/HEAD/packages/platform-express). Updates `@nestjs/core` from 10.4.15 to 11.0.1 - [Release notes](https://github.com/nestjs/nest/releases) - [Commits](https://github.com/nestjs/nest/commits/v11.0.1/packages/core) Updates `@nestjs/platform-express` from 10.4.15 to 11.0.1 - [Release notes](https://github.com/nestjs/nest/releases) - [Commits](https://github.com/nestjs/nest/commits/v11.0.1/packages/platform-express) --- updated-dependencies: - dependency-name: "@nestjs/core" dependency-type: direct:production update-type: version-update:semver-major dependency-group: dependencies - dependency-name: "@nestjs/platform-express" dependency-type: direct:production update-type: version-update:semver-major dependency-group: dependencies ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
Merging to
|
|
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. What is shell access?This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code. Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. What is network access?This module accesses the network. Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Bumps the dependencies group in /examples/nestjs with 2 updates: @nestjs/core and @nestjs/platform-express.
Updates
@nestjs/corefrom 10.4.15 to 11.0.1Commits
0f617d4chore(@nestjs) publish v11.0.1 released6b9feefix: normalize middle wildcards, call path-to-regexp early1299888chore: update readmee19b586chore(@nestjs) publish v11.0.0 release95654f9chore: update package.json6791b6cstyle: address lint errorsdb2a9b5chore: resolve conflictsa24ef96chore(deps): Update opencollective to 0.4.1 under new scope5b091a4chore(deps): upgrade to eventsource v39e5f77cchore: resolve conflictsUpdates
@nestjs/platform-expressfrom 10.4.15 to 11.0.1Commits
0f617d4chore(@nestjs) publish v11.0.1 released6b9feefix: normalize middle wildcards, call path-to-regexp early1299888chore: update readmee19b586chore(@nestjs) publish v11.0.0 release224e0ddchore: upgrade multer95654f9chore: update package.jsondb2a9b5chore: resolve conflicts9e5f77cchore: resolve conflicts8bcd1e5chore: resolve conflicts9267472chore: update copyright years 2025Dependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions