Bump System.CommandLine from 2.0.0-beta1.21308.1 to 2.0.5 (#3702) #1749
BernieWhitedocs.yaml
on: push
Publish docs
8m 24s
Deploy pages
16s
Annotations
11 warnings
|
Publish docs:
src/PSRule.Rules.Azure/Arm/ResourceHelper.cs#L243
Possible null reference argument for parameter 'subscriptionId' in 'string ResourceHelper.CombineResourceId(string subscriptionId, string resourceGroup, string[] resourceType, string[] name, int depth = 2147483647)'.
|
|
Publish docs:
src/PSRule.Rules.Azure/Arm/ResourceHelper.cs#L238
Converting null literal or possible null value to non-nullable type.
|
|
Publish docs:
src/PSRule.Rules.Azure/Arm/ResourceHelper.cs#L238
Converting null literal or possible null value to non-nullable type.
|
|
Publish docs:
src/PSRule.Rules.Azure/Arm/ResourceHelper.cs#L227
Dereference of a possibly null reference.
|
|
Publish docs:
src/PSRule.Rules.Azure/Arm/ResourceHelper.cs#L218
Dereference of a possibly null reference.
|
|
Publish docs:
src/PSRule.Rules.Azure/Arm/Deployments/TemplateContext.cs#L55
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Publish docs:
src/PSRule.Rules.Azure/Pipeline/Export/PolicyAssignmentExpandVisitor.cs#L55
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Publish docs:
src/PSRule.Rules.Azure/Pipeline/Export/PolicyAssignmentExpandVisitor.cs#L50
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Publish docs:
src/PSRule.Rules.Azure/Pipeline/Export/ExportDataContext.cs#L94
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Publish docs:
src/PSRule.Rules.Azure.BuildTool/ClientBuilder.cs#L41
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Deploy pages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/configure-pages@983d7736d9b0ae728b81ab479565c72886d7745b, actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|