build(deps): bump @nestjs/core from 8.0.6 to 11.1.18#533
build(deps): bump @nestjs/core from 8.0.6 to 11.1.18#533dependabot[bot] wants to merge 1 commit intodevelopfrom
Conversation
Bumps [@nestjs/core](https://github.com/nestjs/nest/tree/HEAD/packages/core) from 8.0.6 to 11.1.18. - [Release notes](https://github.com/nestjs/nest/releases) - [Commits](https://github.com/nestjs/nest/commits/v11.1.18/packages/core) --- updated-dependencies: - dependency-name: "@nestjs/core" dependency-version: 11.1.18 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
🤖 Augment PR SummarySummary: Updates the API service’s NestJS runtime dependency. Changes:
Technical Notes: This is a major NestJS upgrade for 🤖 Was this summary useful? React with 👍 or 👎 |
| "@nestjs/common": "^10.4.6", | ||
| "@nestjs/config": "^3.3.0", | ||
| "@nestjs/core": "^10.4.6", | ||
| "@nestjs/core": "^11.1.18", |
There was a problem hiding this comment.
api/package.json:38 bumps @nestjs/core to v11, but @nestjs/common and @nestjs/platform-express remain at v10.4.6; @nestjs/core@11 declares peer deps on @nestjs/common/@nestjs/platform-express ^11.0.0, so this mixed major-version set is likely to cause install-time peer-dependency errors/warnings or runtime incompatibilities.
Severity: high
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| "@nestjs/common": "^10.4.6", | ||
| "@nestjs/config": "^3.3.0", | ||
| "@nestjs/core": "^10.4.6", | ||
| "@nestjs/core": "^11.1.18", |
There was a problem hiding this comment.
api/package.json:38 / PR metadata: the PR title/description says this bumps @nestjs/core from 8.0.6, but the diff shows it was ^10.4.6 in this repo; that mismatch could make the upgrade scope confusing to reviewers/release notes.
Severity: low
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
There was a problem hiding this comment.
1 issue found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="api/package.json">
<violation number="1" location="api/package.json:38">
P1: This upgrades only `@nestjs/core` to v11, but the rest of the Nest stack here still requires `@nestjs/core` v10. That leaves `api/package.json` with incompatible peer dependencies and an unsupported mixed-major Nest setup.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| "@nestjs/common": "^10.4.6", | ||
| "@nestjs/config": "^3.3.0", | ||
| "@nestjs/core": "^10.4.6", | ||
| "@nestjs/core": "^11.1.18", |
There was a problem hiding this comment.
P1: This upgrades only @nestjs/core to v11, but the rest of the Nest stack here still requires @nestjs/core v10. That leaves api/package.json with incompatible peer dependencies and an unsupported mixed-major Nest setup.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At api/package.json, line 38:
<comment>This upgrades only `@nestjs/core` to v11, but the rest of the Nest stack here still requires `@nestjs/core` v10. That leaves `api/package.json` with incompatible peer dependencies and an unsupported mixed-major Nest setup.</comment>
<file context>
@@ -35,7 +35,7 @@
"@nestjs/common": "^10.4.6",
"@nestjs/config": "^3.3.0",
- "@nestjs/core": "^10.4.6",
+ "@nestjs/core": "^11.1.18",
"@nestjs/jwt": "^10.2.0",
"@nestjs/passport": "^10.0.3",
</file context>
| "@nestjs/core": "^11.1.18", | |
| "@nestjs/core": "^10.4.6", |
Greptile SummaryThis PR bumps only Confidence Score: 4/5Not safe to merge — @nestjs/core v11 conflicts with the remaining v10 NestJS packages, risking runtime failures One clear P1 finding: incomplete NestJS major-version upgrade creates peer dependency mismatches that will cause runtime errors and type mismatches between shared internal interfaces api/package.json — all @nestjs/* dependencies must be co-upgraded to v11 Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["@nestjs/core v11.1.18"] -->|"peer requires"| B["@nestjs/common ^11.0.0"]
C["@nestjs/common ^10.4.6 installed"] -->|"does NOT satisfy"| B
B --> D["Peer dependency conflict"]
A -->|"peer requires"| E["@nestjs/platform-express ^11.0.0"]
F["@nestjs/platform-express ^10.4.6 installed"] -->|"does NOT satisfy"| E
E --> D
Reviews (1): Last reviewed commit: "build(deps): bump @nestjs/core from 8.0...." | Re-trigger Greptile |
| "@nestjs/common": "^10.4.6", | ||
| "@nestjs/config": "^3.3.0", | ||
| "@nestjs/core": "^10.4.6", | ||
| "@nestjs/core": "^11.1.18", |
There was a problem hiding this comment.
Incomplete NestJS major-version upgrade
Only @nestjs/core is bumped to v11 while @nestjs/common, @nestjs/platform-express, @nestjs/testing, and @nestjs/cli all remain at v10. @nestjs/core v11 declares @nestjs/common: "^11.0.0" as a peer dependency, but package.json constrains it to ^10.4.6. These packages share internal interfaces (NestContainer, ModuleRef, token types) that changed between major versions — this mismatch will cause runtime errors. All @nestjs/* packages must be co-upgraded to v11.
Rule Used: When updating dependencies via automated PRs (like... (source)
Learnt From
ever-co/ever-traduora#478



Bumps @nestjs/core from 8.0.6 to 11.1.18.
Release notes
Sourced from
@nestjs/core's releases.... (truncated)
Commits
3c1cc5fchore(release): publish v11.1.18 release0f962c7fix(core): sanitize sse message94aa424Merge pull request #16679 from nestjs/renovate/path-to-regexp-8.x368691cfix(core): prevent injector hang when design:paramtypes is missing25d4fdefix(deps): update dependency path-to-regexp to v8.4.25c0b11efix(deps): update dependency path-to-regexp to v8.4.1f7d4460Merge pull request #16637 from JakobStaudinger/moduleref-create-transient-sco...d0a9dc9fix(deps): update dependency path-to-regexp to v8.4.04677434feat(core): exportIEntryNestModuletype7493b94fix(core): dependency injection edge case with moduleref.createDependabot 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 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.
Summary by cubic
Upgrade
@nestjs/coreto v11.1.18 to pick up Nest 11 fixes and updated routing utilities. This is a major bump; other Nest packages should be aligned to v11.Dependencies
path-to-regexp@8.4.2,tslib@2.8.1.@nuxtjs/opencollectivewith@nuxt/opencollective(usesconsola@^3).node-fetch@^2.6.1from the tree.Migration
@nestjs/common,@nestjs/platform-express, and other Nest packages to v11.Written for commit 46d5b1f. Summary will update on new commits.