Bump vite from 6.2.2 to 6.4.2 in /examples/CRUD/Frontend#42
Open
dependabot[bot] wants to merge 1 commit into
Open
Bump vite from 6.2.2 to 6.4.2 in /examples/CRUD/Frontend#42dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Annotations
1 error and 11 warnings
|
|
|
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
tests/Oxpecker.Tests/Helpers.Tests.fs#L111
Nullness warning: A non-nullable 'System.Object' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
|
|
tests/Oxpecker.Tests/Helpers.Tests.fs#L111
Nullness warning: A non-nullable 'System.Object' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
|
|
tests/Oxpecker.Tests/Helpers.Tests.fs#L105
Nullness warning: A non-nullable 'System.Object' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
|
|
tests/Oxpecker.Tests/Helpers.Tests.fs#L105
Nullness warning: A non-nullable 'System.Object' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
|
|
tests/Oxpecker.Tests/Helpers.Tests.fs#L99
Nullness warning: A non-nullable 'System.Object' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
|
|
tests/Oxpecker.Tests/Helpers.Tests.fs#L99
Nullness warning: A non-nullable 'System.Object' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
|
|
tests/Oxpecker.Tests/Helpers.Tests.fs#L93
Nullness warning: A non-nullable 'System.Object' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
|
|
tests/Oxpecker.Tests/Helpers.Tests.fs#L93
Nullness warning: A non-nullable 'System.Object' was expected but this expression is nullable. Consider either changing the target to also be nullable, or use pattern matching to safely handle the null case of this expression.
|
|
examples/MCP/Client/Program.fs#L83
This construct is experimental. This warning can be disabled using '--nowarn:57' or '#nowarn "57"'.
|
|
examples/MCP/Client/Program.fs#L73
This construct is experimental. This warning can be disabled using '--nowarn:57' or '#nowarn "57"'.
|
The logs for this run have expired and are no longer available.
Loading