Bump some packages to 4.1.0 #288
Annotations
11 warnings
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Run build.fsx:
Fun.Blazor.HotReload/Interpreter.fs#L1103
This construct is deprecated. Formatter-based serialization is obsolete and should not be used.
|
Run build.fsx:
Fun.Htmx/Core.fs#L308
Lowercase literal 'abort' is being shadowed by a new pattern with the same name. Only uppercase and module-prefixed literals can be used as named patterns.
|
Run build.fsx:
Fun.Htmx/Core.fs#L308
Lowercase literal 'abort' is being shadowed by a new pattern with the same name. Only uppercase and module-prefixed literals can be used as named patterns.
|
Run build.fsx:
Fun.Blazor.HotReload/Interpreter.fs#L1103
This construct is deprecated. Formatter-based serialization is obsolete and should not be used.
|
Run build.fsx:
Fun.Blazor.HotReload/Interpreter.fs#L1103
This construct is deprecated. Formatter-based serialization is obsolete and should not be used.
|
Run build.fsx:
Fun.Htmx/Core.fs#L308
Lowercase literal 'abort' is being shadowed by a new pattern with the same name. Only uppercase and module-prefixed literals can be used as named patterns.
|
Run build.fsx:
Fun.Htmx/Core.fs#L308
Lowercase literal 'abort' is being shadowed by a new pattern with the same name. Only uppercase and module-prefixed literals can be used as named patterns.
|
Run build.fsx:
Fun.Blazor.HotReload/Interpreter.fs#L1103
This construct is deprecated. Formatter-based serialization is obsolete and should not be used.
|
Run build.fsx:
Fun.Blazor.HotReload/Interpreter.fs#L1103
This construct is deprecated. Formatter-based serialization is obsolete and should not be used.
|
Run build.fsx:
Fun.Blazor.Cli/Watch/Processor.fs#L191
Note: Lambda-lifting optimizations have not been applied because of the use of this local constrained generic function as a first class value. Adding type constraints may resolve this condition.
|
Loading