GitHub’s new OIDC support for repository custom properties is more than a convenience feature. It gives platform teams a cleaner way to express cloud access around repo attributes instead of maintaining brittle allowlists one workflow at a time.
Tekton Pipeline 1.10.1 is a modest patch release with one notable fix, but the release still stands out for something more important: the project keeps shipping attestation guidance right in the notes. For platform teams, that is the pattern worth adopting even when the diff itself is small.
GitHub’s new pre-commit ecosystem support turns one of the most annoying sources of silent repo drift into a first-class dependency workflow. The win is not just freshness. It is making hook upgrades reviewable, grouped, and testable like any other supply-chain change.
GitHub added 28 new secret detectors, broadened default push protection, and introduced more validity checks in March 2026. The real story is operational: secret scanning is becoming a faster feedback system for SaaS sprawl, not just a cleanup tool after a leak.
GitHub’s latest CodeQL release adds Java 26 support, better Maven version selection, and query updates across multiple languages. The operational takeaway is simple: code scanning accuracy increasingly depends on matching real build conditions, not just running static analysis somewhere in CI.
GitHub’s new ‘Lock advisory’ action lets repo admins freeze draft security advisories and private vulnerability reports while discussion continues in comments. For DevSecOps teams, it’s a governance primitive: reduce accidental edits, preserve triage decisions, and keep the record stable before publication.
GitHub says Copilot code review is now generally available on an agentic, tool-calling architecture that can pull broader repository context on demand — and it runs on GitHub Actions. That combination shifts cost, governance, and security considerations for engineering orgs. Here’s how to evaluate it, especially if you use self-hosted runners.
Flux 2.8 ships Helm v4 support (including server-side apply) and pushes more deployments toward kstatus-style readiness. That combination changes the operational contract of GitOps: fewer false ‘healthy’ signals, better drift visibility, and sharper rollback decisions.
GitHub now supports assigning Dependabot alerts to specific users (GA). That sounds small—but it’s the missing piece that lets teams operationalize dependency remediation the same way they do incidents: ownership, queues, automation, and reporting.
GitHub is deprecating several Copilot models (including GPT-5.1) and changing required network routing for Copilot coding agent. If you run agents on self-hosted runners, your allowlists and model policies need attention now.
GitHub is rolling out macos-26 GitHub-hosted runners. Here’s why it matters for iOS/macOS builds, code signing, supply-chain controls, and reproducibility in CI.
GitHub-hosted runners now offer macos-26 generally available. Treat this like a platform migration: validate toolchains, codesigning, caches, and flaky tests before the default image shifts.
GitHub Actions now supports uploading and downloading non-zipped artifacts—reducing friction for single-file outputs, browser-based inspection, and ‘double zip’ anti-patterns. Here’s what changed, how to adopt it safely, and why it’s a useful signal for platform engineering teams standardizing CI at scale.
Flux 2.8 lands Helm v4 support (SSA + kstatus health checks), reduces MTTR by canceling health checks when new revisions appear, and expands GitOps feedback loops with PR/MR comment providers and a new Flux Operator Web UI.
Flux 2.8 GA ships with Helm v4 support, bringing server-side apply and kstatus-based health checking to Helm releases. Here’s why that’s bigger than it sounds—and how platform teams should approach the upgrade.
GitHub is tightening the screws on enterprise governance: enterprise-defined custom org roles are GA, and IP allow lists now extend deeper into EMU user namespaces. Here’s what it changes for platform teams.
GitHub is rolling Copilot usage metrics down from enterprise to organization scope, enabling least-privilege reporting. For platform and security teams, this is the missing layer for governing AI coding tools without centralizing all visibility at the enterprise tier.
GitHub is previewing an organization-level Copilot usage metrics dashboard. For platform engineering, it’s a sign that AI tooling will be governed like any other shared service: measured, costed, and optimized. Here’s what to track and how to operationalize it.
GitHub’s workflow dispatch API can now return run metadata, eliminating brittle polling and guesswork in automation. Here’s why it matters for platform teams building ChatOps, self-service, and internal developer portals.
GitHub’s workflow_dispatch API can now return run IDs. That makes self-service CI/CD safer and more observable, enabling tighter coupling between portal actions, audit logs, and rollout status.
