refactor: Bump js-yaml from 4.3.0 to 4.3.1 #245
dependabot[bot]Annotations
22 warnings
|
.NET 9.0
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
.NET 9.0:
Parse/Platform/Objects/ParseObject.cs#L129
The variable 'ex' is declared but never used
|
|
.NET 9.0:
Parse/Platform/Users/ParseUser.cs#L113
The variable 'ex' is declared but never used
|
|
.NET 9.0:
Parse/Platform/Users/ParseUser.cs#L31
The variable 'ex' is declared but never used
|
|
.NET 9.0:
Parse/Platform/Cloud/ParseCloudCodeController.cs#L40
'Uri.EscapeUriString(string)' is obsolete: 'Uri.EscapeUriString can corrupt the Uri string in some cases. Consider using Uri.EscapeDataString for query string components instead.' (https://aka.ms/dotnet-warnings/SYSLIB0013)
|
|
.NET 9.0:
Parse/Platform/Users/ParseCurrentUserController.cs#L95
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
.NET 9.0:
Parse/Infrastructure/Utilities/TaskQueue.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
.NET 9.0:
Parse/Platform/Users/ParseCurrentUserController.cs#L28
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
.NET 9.0:
Parse/Infrastructure/Utilities/JsonUtilities.cs#L377
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
|
.NET 9.0:
Parse/Infrastructure/Data/ParseDataEncoder.cs#L124
XML comment has badly formed XML -- 'End tag was not expected at this location.'
|
|
.NET 9.0:
Parse/Infrastructure/Utilities/JsonUtilities.cs#L376
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'pre'.'
|
|
.NET 8.0
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
.NET 8.0:
Parse/Platform/Objects/ParseObject.cs#L129
The variable 'ex' is declared but never used
|
|
.NET 8.0:
Parse/Platform/Cloud/ParseCloudCodeController.cs#L40
'Uri.EscapeUriString(string)' is obsolete: 'Uri.EscapeUriString can corrupt the Uri string in some cases. Consider using Uri.EscapeDataString for query string components instead.' (https://aka.ms/dotnet-warnings/SYSLIB0013)
|
|
.NET 8.0:
Parse/Platform/Users/ParseUser.cs#L113
The variable 'ex' is declared but never used
|
|
.NET 8.0:
Parse/Platform/Users/ParseUser.cs#L31
The variable 'ex' is declared but never used
|
|
.NET 8.0:
Parse/Platform/Users/ParseCurrentUserController.cs#L95
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
.NET 8.0:
Parse/Infrastructure/Utilities/TaskQueue.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
.NET 8.0:
Parse/Platform/Users/ParseCurrentUserController.cs#L28
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
.NET 8.0:
Parse/Infrastructure/Utilities/JsonUtilities.cs#L377
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
|
.NET 8.0:
Parse/Infrastructure/Data/ParseDataEncoder.cs#L124
XML comment has badly formed XML -- 'End tag was not expected at this location.'
|
|
.NET 8.0:
Parse/Infrastructure/Utilities/JsonUtilities.cs#L376
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'pre'.'
|