Repository navigation
build(deps): bump mcp/sdk from 0.9.0 to 0.10.0 - #4919
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Annotations
8 errors, 10 warnings, and 11 notices
|
Run Mago
Process completed with exit code 1.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Service/McpServer/McpSdkRuntime.php#L88
Could not infer a precise return type for function `phpMyFAQ\Service\McpServer\McpSdkRuntime::buildServer`. Saw type `mixed`.
>Type inferred as `mixed` here.
The analysis could not determine a specific type for the value returned here, resulting in `mixed`. This can happen with complex code paths or unannotated data.
Help: Add specific type hints to variables, parameters, or properties involved in calculating the return value. Consider adding a specific return type declaration to the function signature to catch potential mismatches earlier.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Service/McpServer/McpSdkRuntime.php#L105
Attempting to call method `build()` on a non-object type (`mixed`).
>Cannot call method here
>This expression has type `mixed`
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Service/McpServer/McpSdkRuntime.php#L94
Attempting to call method `addTool()` on a non-object type (`mixed`).
>Cannot call method here
>This expression has type `mixed`
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Service/McpServer/McpSdkRuntime.php#L89
Attempting to call method `setServerInfo()` on a non-object type (`mixed`).
>Cannot call method here
>This expression has type `mixed`
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Service/McpServer/McpSdkRuntime.php#L88
Method `builder` does not exist on type `Mcp\Server`.
>This method selection is invalid
>This expression has type `Mcp\Server`
Help: Ensure the `builder` method is defined in the `Mcp\Server` class-like.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Service/McpServer/McpSdkRuntime.php#L84
Cannot find class, interface, enum, or type alias `Mcp\Server`.
>`Mcp\Server` is not defined in the current codebase
This error occurs when a type is referenced but not found in any analyzed source files or stubs.
If this type comes from an optional dependency or extension, you can safely suppress this issue using `@mago-ignore` or `@mago-expect`.
Help: Verify the type name is spelled correctly, the file containing it is included in analysis, and any required `use` statements are present.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Service/McpServer/McpSdkRuntime.php#L41
Attempting to call method `run()` on a non-object type (`unknown-ref(Mcp\Server)`).
>Cannot call method here
>This expression has type `unknown-ref(Mcp\Server)`
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Api/QuestionController.php#L122
Literal argument `''` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: '')`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Api/QuestionController.php#L121
Literal argument `''` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: '')`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Administration/Api/InstanceController.php#L137
Literal argument `1` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: 1)`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Administration/Api/InstanceController.php#L137
Literal argument `''` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: '')`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Administration/Api/InstanceController.php#L128
Literal argument `''` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: '')`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Administration/AdminLogRepository.php#L110
Literal argument `'id'` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: 'id')`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Api/HealthController.php#L48
Literal argument `'no-store'` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: 'no-store')`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Administration/SessionKeepAliveController.php#L44
Literal argument `'en'` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: 'en')`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/User/TwoFactor.php#L181
Literal argument `200` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: 200)`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Administration/Api/MediaBrowserController.php#L66
Literal argument `''` should be passed as a named argument for clarity.
>This literal is being passed positionally.
Passing literals positionally can make code less clear, especially with booleans, numbers, or `null`.
Help: Consider using a named argument instead: `function_name(param: '')`.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Bootstrap/ConfigDirectoryResolver.php#L96
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Bootstrap/ConfigDirectoryResolver.php#L85
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Bootstrap/ConfigDirectoryResolver.php#L71
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Setup/Update.php#L203
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Setup/Migration/Versions/Migration400Alpha.php#L48
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Setup/AbstractSetup.php#L72
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/SetupController.php#L249
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Frontend/SetupController.php#L197
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Frontend/SetupController.php#L149
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
Run Mago:
phpmyfaq/src/phpMyFAQ/Controller/Administration/Api/InstanceController.php#L115
Redundant cast to `(string)`: the expression already has this type.
>This expression already has type `string`.
Casting a value to a type it already possesses has no effect.
Help: Remove the redundant `(string)` cast.
|
|
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
|
background
wait
wait-all
cancel
parallel
Loading