Skip to content

feat(cli): compile page code-behind safely #516

feat(cli): compile page code-behind safely

feat(cli): compile page code-behind safely #516

Triggered via pull request May 8, 2026 02:53
Status Success
Total duration 6m 43s
Artifacts

codeql.yml

on: pull_request
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
Analyze (csharp)
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@v4, github/codeql-action/analyze@v3, github/codeql-action/init@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/
Analyze (csharp): src/BlazorWebFormsComponents/Shims/HttpUtility.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Analyze (csharp): src/BlazorWebFormsComponents/Shims/HttpUtility.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Analyze (csharp): src/BlazorWebFormsComponents/Shims/HttpUtility.cs#L9
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Analyze (csharp): src/BlazorWebFormsComponents/Shims/HttpUtility.cs#L9
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Analyze (csharp): src/BlazorWebFormsComponents/Shims/HttpUtility.cs#L7
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Analyze (csharp): src/BlazorWebFormsComponents/Shims/HttpUtility.cs#L7
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Analyze (csharp): src/BlazorWebFormsComponents.Analyzers/PageClientScriptUsageAnalyzer.cs#L32
The diagnostic message should not contain any line return character nor any leading or trailing whitespaces and should either be a single sentence without a trailing period or a multi-sentences with a trailing period
Analyze (csharp): src/BlazorWebFormsComponents.Analyzers/RunatServerAnalyzer.cs#L26
The diagnostic message should not contain any line return character nor any leading or trailing whitespaces and should either be a single sentence without a trailing period or a multi-sentences with a trailing period
Analyze (csharp): src/BlazorWebFormsComponents.Analyzers/ScriptManagerUsageAnalyzer.cs#L34
The diagnostic message should not contain any line return character nor any leading or trailing whitespaces and should either be a single sentence without a trailing period or a multi-sentences with a trailing period
Analyze (csharp): src/BlazorWebFormsComponents.Analyzers/EventHandlerSignatureAnalyzer.cs#L28
The diagnostic message should not contain any line return character nor any leading or trailing whitespaces and should either be a single sentence without a trailing period or a multi-sentences with a trailing period
Analyze (csharp)
Cannot retrieve the full diff because there are too many (300) changed files in the pull request.
Analyze (csharp)
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/