Coding Tools
GitHub scans Actions logs for leaked secrets
GitHub Changeloghigh confidence
Why it matters
- →Closes a common security gap where CI/CD logs accidentally expose credentials.
- →Alerts persist after log deletion, ensuring long-term visibility of past leaks.
- →Requires Enterprise Advanced Security license, limiting immediate adoption for smaller teams.
GitHub is now scanning GitHub Actions workflow logs for leaked secrets, adding them to the existing secret scanning alert list alongside code and issues. Available in public preview for GitHub Enterprise Cloud customers with Advanced Security or Secret Protection, the feature runs validity checks on supported secret types after a workflow completes. Alerts remain accessible even if logs are deleted, though the scan does not backfill historical data or detect generic patterns. The policy is disabled by default and requires manual enablement via enterprise settings.
Read originalThe story around this
Earlier coverage that leads up to this article, and what followed. Lines connect each piece to the closest one after it, converging here.
How we got here
- 1GitHub Enhances Secret Scanning and Monitoring
GitHub Changelog · July 15, 2026 · Same story
- 2GitHub Secret Scanning: Base64 Tokens & Audit Log Changes
GitHub Changelog · October 20, 2026 · Same story
More from GitHub Changelog
© GitHub ChangelogCoding Toolscoding
GitHub expands issue types to personal accounts
GitHub finally brings enterprise-grade planning structures to individual developers. Personal repositories now support customizable issue types and fields, allowing solo maintainers to standardize workflows with up to 25 distinct categories. This closes a long-standing gap where only organizations could enforce structured data schemas for bug tracking and feature management. The move signals that GitHub is treating personal open-source projects with the same operational seriousness as corporate codebases.
GitHub Changelog
© GitHub ChangelogMore in Coding Tools
Coding Toolscoding
Claude Code v2.1.323 adds experimental Code Mode and plugin safety
This release quietly introduces Code Mode, an opt-in feature where Claude writes JavaScript to call its own tools, marking a shift toward more autonomous agent-like behavior within the CLI. The update also hardens the plugin ecosystem by enforcing version ranges and adding strict TypeScript type checking for hooks, which should significantly reduce instability from third-party extensions. Beyond these features, the changelog is dominated by critical fixes for authentication drift in background sessions and memory leaks when handling large files, stabilizing the tool for heavy enterprise use.
Claude Code Releases
Coding Toolscoding
llama.cpp b12336 fixes HunyuanVL crash
This release quietly patches a critical memory overflow in the mtmd module that caused crashes when loading HunyuanVL models. The issue stemmed from F64 position embeddings overflowing an F32 buffer, a subtle bug that broke multimodal inference for users relying on this specific architecture. By enforcing strict F32 requirements, llama.cpp stabilizes support for Tencent's vision-language model without adding new features or changing the core API. It’s a necessary maintenance update that keeps local multimodal workflows from breaking unexpectedly.
