CodeQL #353
Annotations
16 warnings
Analyze (javascript)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Analyze (javascript)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, github/codeql-action/init@v2, actions/setup-dotnet@v3, github/codeql-action/autobuild@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Analyze (javascript)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
|
Analyze (csharp)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Analyze (csharp)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, github/codeql-action/init@v2, actions/setup-dotnet@v3, github/codeql-action/autobuild@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Analyze (csharp)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
|
Analyze (csharp):
1_CS/ErrorsAndExceptions/RethrowExceptions/Program.cs#L4009
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
|
Analyze (csharp):
1_CS/ErrorsAndExceptions/SolicitColdCall/Program.cs#L15
The local function 'ColdCallFileReaderLoop2' is declared but never used
|
Analyze (csharp):
1_CS/ErrorsAndExceptions/RethrowExceptions/Program.cs#L4009
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
|
Analyze (csharp):
1_CS/ErrorsAndExceptions/SolicitColdCall/Program.cs#L15
The local function 'ColdCallFileReaderLoop2' is declared but never used
|
Analyze (csharp)
A publish profile with the name 'win10-x64.pubxml' was not found in the project. Set the PublishProfile property to a valid file name.
|
Analyze (csharp)
A publish profile with the name 'win10-x64.pubxml' was not found in the project. Set the PublishProfile property to a valid file name.
|
Analyze (csharp):
2_Libs/EFCore/ScaffoldSample/ProCSharpMenus2Context.cs#L28
#warning: 'To protect potentially sensitive information in your connection string, you should move it out of source code. You can avoid scaffolding the connection string by using the Name= syntax to read it from configuration - see https://go.microsoft.com/fwlink/?linkid=2131148. For more guidance on storing connection strings, see http://go.microsoft.com/fwlink/?LinkId=723263.'
|
Analyze (csharp):
2_Libs/EFCore/ScaffoldSample/ProCSharpMenus2Context.cs#L28
#warning: 'To protect potentially sensitive information in your connection string, you should move it out of source code. You can avoid scaffolding the connection string by using the Name= syntax to read it from configuration - see https://go.microsoft.com/fwlink/?linkid=2131148. For more guidance on storing connection strings, see http://go.microsoft.com/fwlink/?LinkId=723263.'
|
Analyze (csharp)
A publish profile with the name 'win10-x86.pubxml' was not found in the project. Set the PublishProfile property to a valid file name.
|
Analyze (csharp)
A publish profile with the name 'win10-x86.pubxml' was not found in the project. Set the PublishProfile property to a valid file name.
|