tag: Codeql · 6 items
- Platform/SRE — Skip
- CI/CD — Plan: Teams running CodeQL on Swift projects will need to update their scanning configuration when adopting macOS 27 or Xcode 27 runners, as Apple has removed Intel x86_64 code from system binaries CodeQL depends on for build tracing. No forced deadline, but plan this alongside any macOS 27 runner migration.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: Pipelines that download codeql-bundle.tar.gz or .tar.zst need to migrate to platform-specific CodeQL bundles; no hard removal date announced yet, so audit your CodeQL download steps and update references to the appropriate per-platform bundle this quarter.
- Leader — Skip
- Signals: deprecation mentioned (no explicit date found)
- Platform/SRE — Skip
- CI/CD — Plan: If your pipelines run CodeQL on ARM64 Linux runners, upgrading to 2.27.0 unlocks native support; also worth evaluating the new Rust security query and expanded Java/Kotlin and C# framework coverage for any affected repositories.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: If your pipelines use CodeQL scanning, upgrading to 2.26.4 improves detection coverage for GitHub Actions security issues and adds Go 1.27 support — schedule the version bump this quarter.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: If you use CodeQL in GitHub Actions, evaluate adopting the new dedicated workflow path to improve run-history clarity and accurate usage reporting — no deadline, but worth scheduling as routine pipeline hygiene.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Plan: If pipelines use CodeQL for code scanning on Swift or Kotlin codebases, upgrade to 2.26.2 to gain language-version coverage for Swift 6.3.3 and Kotlin 2.4.10; no deadline, but worth scheduling this quarter.
- Leader — Skip