Signal / 028 — Home Assistant changes an entity ID without rebuilding the entity
New lifecycle hooks let integrations prepare before entity addition and handle entity-ID changes in place, with a compatibility window for custom integrations.
Signal / 026 — Cloudflare moves log redaction into the export pipe
Logpush Transformers apply SQL filters and field changes before telemetry reaches storage, reducing exported noise while raising new questions about evidence retention.
Signal / 025 — Modern Warfare 4 builds DMZ around a base that remembers
Modern Warfare 4’s extraction mode ties deployments to an evolving Forward Operating Base, three mission styles, and a separate 70-level progression track.
Signal / 027 — GitHub separates who wrote a commit from who pushed it
A limited GitHub Enterprise preview adds durable authenticated pusher identity and an optional rule requiring committer metadata to match the pusher.
Signal / 024 — ZFS replication is a backup path, not a backup policy
Snapshots plus zfs send and receive can build an efficient second copy, but replication still needs separation, verification, and a tested restore route.
Signal / 023 — OpenSSF Scorecard turns repository habits into a security signal
Before adding another dependency, Scorecard can surface risky repository practices—but its number is a prompt for investigation, not an automatic verdict.
Signal / 022 — WebAuthn Level 3 turns passkeys into web infrastructure
W3C’s latest Web Authentication Recommendation gives passkey implementations a firmer shared target—and passwords one less excuse to remain the default.
Signal / 021 — Rockbeasts finds a louder publisher in Critical Role
The rock-band management RPG has a January 2027 window, new voice talent, and a publishing partner built around character-driven chaos.
Signal / 020 — The DNS root changes keys today; validating resolvers need KSK-2024
Today’s DNS root KSK rollover is routine for most users, but self-hosted validating resolvers must trust KSK-2024 or signed domains can fail.
Signal / 019 — Git 2.56 adds a safer way to mark conflicts resolved
Git 2.56 introduces git add –resolved, faster merge-base traversal, and new tools for large repositories and branch cleanup.