-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
build(deps): bump the npm_and_yarn group across 1 directory with 3 updates #1101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
| "jsonwebtoken": "^9.0.2", | ||
| "lodash": "^4.17.21", | ||
| "mastra": "^0.13.2", | ||
| "md5": "^2.3.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: The experimental.proxyTimeout option in next.config.js is incompatible with Next.js 15.4.8.
Severity: CRITICAL | Confidence: High
🔍 Detailed Analysis
The next.config.js file contains experimental.proxyTimeout, which was an experimental feature in earlier Next.js versions but has been removed or made inaccessible in Next.js 14 and 15. This incompatibility will cause a build failure or prevent the application from starting properly when upgraded to Next.js 15.4.8, as the application cannot start successfully with this deprecated configuration.
💡 Suggested Fix
Remove the experimental.proxyTimeout configuration from next.config.js as it is no longer supported in Next.js 15.
🤖 Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: package.json#L173
Potential issue: The `next.config.js` file contains `experimental.proxyTimeout`, which
was an experimental feature in earlier Next.js versions but has been removed or made
inaccessible in Next.js 14 and 15. This incompatibility will cause a build failure or
prevent the application from starting properly when upgraded to Next.js 15.4.8, as the
application cannot start successfully with this deprecated configuration.
Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 339092
…dates Bumps the npm_and_yarn group with 3 updates in the / directory: [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk), [multer](https://github.com/expressjs/multer) and [nodemailer](https://github.com/nodemailer/nodemailer). Updates `@modelcontextprotocol/sdk` from 1.22.0 to 1.24.0 - [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases) - [Commits](modelcontextprotocol/typescript-sdk@1.22.0...1.24.0) Updates `multer` from 1.4.5-lts.2 to 2.0.2 - [Release notes](https://github.com/expressjs/multer/releases) - [Changelog](https://github.com/expressjs/multer/blob/main/CHANGELOG.md) - [Commits](expressjs/multer@v1.4.5-lts.2...v2.0.2) Updates `nodemailer` from 6.10.1 to 7.0.11 - [Release notes](https://github.com/nodemailer/nodemailer/releases) - [Changelog](https://github.com/nodemailer/nodemailer/blob/master/CHANGELOG.md) - [Commits](nodemailer/nodemailer@v6.10.1...v7.0.11) --- updated-dependencies: - dependency-name: "@modelcontextprotocol/sdk" dependency-version: 1.24.0 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: multer dependency-version: 2.0.2 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: nodemailer dependency-version: 7.0.11 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]>
019c044 to
ab1b664
Compare
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
Bumps the npm_and_yarn group with 3 updates in the / directory: @modelcontextprotocol/sdk, multer and nodemailer.
Updates
@modelcontextprotocol/sdkfrom 1.22.0 to 1.24.0Release notes
Sourced from
@modelcontextprotocol/sdk's releases.... (truncated)
Commits
356b7e6chore: bump version for release (#1215)09623e2Merge commit from forkcf51343feat: backwards-compatible createMessage overloads for SEP-1577 (#1212)8204126fix: allow zod 4 transformations (#1213)6083600Modify Origin header validation in validateRequestHeaders (streamableHttp.ts ...a6ee2cbfix: normalize null to undefined in ElicitResultSchema content field (#1204)4b651b8feat: add closeStandaloneSSEStream for GET stream polling (#1203)5ceabfbfix: normalize headers in sse transport (#856)f67fc2ffix: improve SSE reconnection behavior (#1191)fab7e1efeat: add closeSSEStream callback to RequestHandlerExtra (#1166)Updates
multerfrom 1.4.5-lts.2 to 2.0.2Release notes
Sourced from multer's releases.
... (truncated)
Changelog
Sourced from multer's changelog.
Commits
e5db9ca🔖 2.0.2adfeaf6🥅 improve error handlinge259a7e🔖 2.0.135a3272Fixes expressjs/multer#1233. Makes multer handle mi...f897007ci: apply security best practices (#1311)061f4cb📝 list languages in table to prevent GH right-aligning list due to RTL language854d769deps: update dependencies to latest versions (#1328)256da2f♻️ use version tag for CI, fix CI badge, fix references to master/maindd9dde4📝 fix badges in translation files (#1321)dc2a880ci: change branch referenceMaintainer changes
This version was pushed to npm by ulisesgascon, a new releaser for multer since your current version.
Updates
nodemailerfrom 6.10.1 to 7.0.11Release notes
Sourced from nodemailer's releases.
... (truncated)
Changelog
Sourced from nodemailer's changelog.
... (truncated)
Commits
3d17dbechore(master): release 7.0.11 (#1783)15879f8Bumped dev dependenciesb61b9c0fix: prevent stack overflow DoS in addressparser with deeply nested groups4175e4bchore(master): release 7.0.10 (#1776)d882ccfMerge branch 'master' of github.com:nodemailer/nodemailer1d7e4f7Bumped deps10bd871chore: correct typo in variable name (#1773)28dbf3ffix: Increase data URI size limit from 100KB to 50MB and preserve content type92ae1c4chore(master): release 7.0.9 (#1769)c675d9eMerge branch 'master' of github.com:nodemailer/nodemailerMaintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for nodemailer 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 <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 conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.