security: harden CodeQL and toolchain maintenance - #61
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Owner
Author
|
@codex review |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
rodri-oliveira-dev
deleted the
security/issue-60-codeql-sdk-hardening
branch
September 15, 2026 18:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Hardens the repository security baseline in two focused areas:
security-extendedquery suite;global.json.The CodeQL workflow now also resolves the SDK from
global.jsoninstead of using a floating10.0.xselector, keeping static analysis on the same explicit toolchain contract as the rest of the repository.Why
ReliableWebhooks sits on an external-input boundary and processes webhook payloads, signatures, retries, and delivery state. Broader CodeQL security coverage is therefore useful, provided findings are triaged rather than suppressed for pipeline convenience.
The .NET SDK is also a supply-chain dependency: compiler and SDK changes can affect analyzers, restore/build behavior, and package output. Keeping
global.jsonunder Dependabot closes that maintenance gap without mixing SDK upgrades with NuGet or GitHub Actions updates.Changes
queries: security-extended;global.json;dotnet-sdkDependabot entry;SECURITY.md.Validation
main;Closes #60