
GitHub has rolled out a new feature that lets developers customize their CodeQL code scanning setup using a configuration file. This enhancement allows for detailed control over security scans without the need for individual GitHub Actions workflows in each repository. Organizations can maintain a central configuration file, ensuring consistent security practices while allowing for repository-specific adjustments. This feature is now available on GitHub.com and will be included in GitHub Enterprise Server 3.23, offering a scalable solution for managing security across multiple repositories.
Read originalEarlier coverage that leads up to this article, and what followed. Lines connect each piece to the closest one after it, converging here.
GitHub Changelog · July 14, 2026 · Same story
GitHub Changelog · September 3, 2026 · Same story
© GitHub ChangelogGitHub is finally capping the flood of automated junk hitting maintainers' inboxes. By enforcing daily per-user limits on new private vulnerability reports, the platform stops bad actors from burying legitimate security findings under noise. Admins can now set custom caps or whitelist trusted researchers, ensuring that actual threats get seen. This shifts the burden from manual triage to automated gating, protecting open source maintainers without blocking genuine disclosures.
© GitHub ChangelogAnthropic quietly fixed a critical credential leakage bug where MCP error messages were exposing raw API keys in plaintext logs. Beyond the security patch, this release stabilizes the notoriously fragile background agent system by fixing subagent hand-offs and connection stalls that previously caused silent failures. The update also tightens session management for cloud environments, ensuring large transcripts actually load instead of hanging indefinitely. It’s a maintenance-heavy release, but essential for anyone running complex, multi-step automated workflows.
This update shifts Claude Code from a simple CLI wrapper to a more extensible platform by introducing 'Claude Mods,' allowing plugins to modify deeper behavior rather than just adding tools. The inclusion of a built-in 'You should know' side agent that flags potential oversights is a notable step toward autonomous oversight within the coding workflow. Beyond features, the release addresses critical stability issues in remote sessions and significantly improves accessibility for screen reader users, making the tool more robust for enterprise and diverse developer environments.
GitHub is killing the free-text black hole for private vulnerability reports by mandating structured fields. Reporters must now provide a summary, details, impact assessment, and a proof of concept with at least 150 characters, forcing signal over noise. The platform allows custom forms via YAML to tailor these requirements, while also introducing an AI disclosure checkbox to track automated submissions. This shift moves security triage from manual parsing of vague text to structured data that can be programmatically reviewed or integrated into existing workflows.