[prpixie]

Description

How Has This Been Tested

• All unit tests pass.
• All integration tests pass.
• Manual Testing:

Types of changes

• Docs change
• Refactoring
• Dependency upgrade
• Additional Unit Tests\Integration Tests
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing
  functionality to change)
• Removed no-longer used code

Deployment Configuration Changes

• Requires deployment configuration changes as specified below and in CHANGELOG.md

Checklist

• I have added tests to cover my changes.
• Unreleased section of CHANGELOG.md has been updated with details of this PR.
• No user-controlled or step-output value is string-interpolated directly into a run:/script: body (workflow or composite action); pass it via step-level env: and reference $VAR (bash) or process.env.VAR (github-script) instead.

[credfeto]

Roslyn analyzer findings

✅ No findings.

[dnyw4l3n13]

Required check build-pre-release failed: the job reports SOURCE_PUSH_TOKEN is required but not set and AWS key needed for CloudFormation template validation is not set. This looks like missing secrets for the Dependabot-triggered run (an environment issue, not a code issue). Marking Blocked; secrets/CI config need a human.

[dnyw4l3n13]

Rebased onto origin/main (conflicts in csproj/CHANGELOG resolved by keeping main and re-applying the Threading.Analyzers 18.12.1 bump); force-pushed. Next: CI, then review phases.

[dnyw4l3n13]

Required check build-pre-release still fails after the rebase: the run reports 'AWS key needed for CloudFormation template validation is not set' (and SOURCE_PUSH_TOKEN unset). This is missing secrets for the bot-triggered run, not a code problem, so no code fix is possible from here. Marking Blocked: a human needs to provide the secrets or re-run the check with them.