
GitHub has moved workflow execution protections for Actions from public preview to general availability across Enterprise, organization, and repository levels. The update introduces workflow file targeting for granular policy application, an Insights dashboard for auditing rule impact, and a REST API for programmatic management. Crucially, GitHub will automatically enforce a default rule disabling pull_request_target events in public repositories starting November 2, 2026, to mitigate secret exfiltration risks from untrusted code execution.
Read original
© GitHub ChangelogGitHub is finally giving enterprise admins the granular data needed to measure actual AI adoption rather than just license utilization. The new dashboard and API breakdowns distinguish between passive code reviews triggered automatically and active agent edits or CLI usage, revealing which tools developers actually integrate into their daily workflows. By tracking rolling 28-day populations per adoption phase, organizations can now pinpoint exactly where training is needed instead of guessing based on broad engagement numbers. This shift from counting seats to measuring specific feature interaction marks a maturation in how AI productivity is quantified at scale.
© GitHub ChangelogGitHub is finally giving enterprise admins visibility into how developers actually use Copilot CLI customizations. The new API fields track interaction counts and distinct usage for skills, custom agents, MCP servers, slash commands, and plugins across per-user and aggregate reports. This moves beyond simple seat utilization to measure which automations are gaining traction and where enablement gaps exist. It’s a necessary step for justifying AI infrastructure spend, though the privacy-preserving anonymization of customer-defined names limits granular auditing.
© GitHub ChangelogThe default runner for GitHub Actions is shifting from Ubuntu 24.04 to 26.04, a move that will silently update workflows using the ubuntu-latest label between October and November 2026. This isn't just a patch; it's a full OS upgrade that removes or updates core tools, meaning builds relying on specific package versions could break without warning. Developers need to proactively pin their runners to ubuntu-24.04 if they aren't ready, or test against the new image now to avoid mid-migration failures. The window is wide, but the risk of silent breakage makes this a mandatory maintenance task for any active CI/CD pipeline.
This release quietly extends llama.cpp's hardware support to the latest NVIDIA and AMD stacks. By shipping native binaries for CUDA 13 and ROCm 10, it ensures compatibility with newer GPU architectures without requiring users to compile from source. The inclusion of both CUDA versions side-by-side is a pragmatic move for enterprise environments managing mixed infrastructure. While no new model formats are introduced, this update keeps the runtime relevant as hardware vendors push their latest drivers.
This release quietly cements llama.cpp as the universal inference runtime by finally supporting NVIDIA's latest CUDA 13 stack alongside AMD's ROCm 10. For the first time, users on cutting-edge hardware can run local models without being forced into legacy driver versions or waiting for vendor-specific optimizations. The inclusion of both CUDA 12 and 13 binaries side-by-side removes a major friction point for developers managing mixed environments. While no new model architectures are added, this infrastructure update ensures compatibility with the fastest consumer and data center GPUs hitting the market right now.
This release patches a subtle but critical bug where embedding a GGUF file inside another container caused tensor data corruption due to misaligned memory mapping. The fix ensures the data section is aligned relative to the GGUF header rather than the outer file offset, preventing silent errors that could ruin inference results. It also adds support for loading LoRA adapters via FILE pointers and disables mmap with a warning when alignment issues are detected. This stabilizes llama.cpp for complex packaging scenarios where models are bundled within larger archives or custom formats.