CodeQL 2.25.6 Releases with Swift 6.3.2 Support and Improved C# Analysis Coverage
The latest release of CodeQL version 2.25.6 is now available, bringing critical updates for teams utilizing GitHub's native static analysis and code scanning capabilities. This release integrates comprehensive compatibility with Swift 6.3.2, ensuring that modern iOS and macOS development pipelines can be analyzed for security vulnerabilities without interruption. In addition to Swift updates, this version expands the scope of static analysis coverage for C# codebases, detecting a wider array of structural and logic security issues.
Related tools
Recommended tools for this topic
These picks prioritize high-intent tools relevant to this topic. Some links may include partner or affiliate tracking.
Strong fit for AI, backend, and frontend readers looking for an AI-first coding workflow.
View CursorHigh-value hosting and deployment path for frontend and cloud readers.
View VercelA strong security and edge platform match across CDN, Zero Trust, and app protection.
View CloudflareComparison
| Aspect | Before / Alternative | After / This |
|---|---|---|
| Swift support | Limited to older Swift versions, causing scanning gaps in modern iOS apps | Full support for Swift 6.3.2 compiled code |
| C# scanning coverage | Standard analysis patterns with potential gaps in recent framework features | Improved coverage and refined query heuristics for C# repositories |
| Integration status | Older CodeQL version dependency in local execution runners | Upgraded defaults in GitHub-hosted runners and actions |
Action Checklist
- Update your GitHub Actions workflows to use CodeQL Action v3 or specify version 2.25.6 to receive the latest analysis engines. GitHub-hosted runners will adopt this automatically, but self-hosted runners may need manual configuration.
- Verify Swift 6.3.2 compilation compatibility within your active CI/CD pipelines. Ensure your build steps align with the version parameters expected by CodeQL.
- Monitor C# scanning alerts for new or resolved security findings triggered by the updated coverage rules. Expect potential changes in your security dashboard due to the improved heuristics.
Source: GitHub Changelog
This page summarizes the original source. Check the source for full details.
