Find published research by company, product, platform or technology.
Showing 81–100 of 171 dossiers
The change turns cache poisoning from mostly a workflow-design warning into an enforceable permission boundary. Teams can let untrusted jobs restore caches without writing them, prevent reusable workflows from escalating cache access and isolate jobs that only need to publish cache entries.
The corrected rollout matters for supply-chain configuration: teams can still remove PATs for qualifying GitHub Packages, but GitHub changed the precedence model after some npm update jobs were mistakenly routed through GitHub Packages.
Microsoft's Agent Host already detached coding-agent sessions from one editor window. Agent Merge shows what that architecture enables: a long-running worker can keep cycling through PR feedback and CI state rather than stopping after one code-generation turn. The feature is still Preview and needs the same review, permission and side-effect controls as any autonomous delivery loop.
Manifest V2 was already disabled for modern Chrome users. The August 31 change closes the remaining Web Store path, turning any still-pinned legacy install into an effectively frozen artifact with no Store update or reinstall route.
GitHub’s new token-type controls let responders revoke PATs, SSH keys, OAuth app tokens or GitHub App user tokens selectively instead of invalidating every credential belonging to a user.
Cloudflare’s new MCP controls turn TLS-inspected Gateway traffic into an inventory and policy surface for remote MCP use, while explicitly leaving local stdio, off-network and uninspected traffic outside visibility.
Tailcat is deliberately smaller than a tailnet: peers exchange a short connection token out of band, then Tailscale’s data-plane code tries direct UDP and falls back to DERP. The trade-off is that the new tool has no stability or service guarantees yet.
Azure’s old PostgreSQL versions do not switch off on September 1, but they do become a paid legacy choice. Extended Support is automatic, billed by vCore-hour for running servers, and cannot be declined while an unsupported engine version remains in use.
Agent Identity is moving from a standalone credential boundary into a mainstream serverless runtime. Cloud Run can now assign agent identities and register agents/MCP servers automatically, reducing custom discovery and identity plumbing while keeping the runtime integration itself in Preview.
AWS has added a `REFERENCE` mode for Lambda deployment packages. It eliminates duplicate managed copies, raises the default managed-storage quota to 300GB, and gives teams direct control over encryption, lifecycle and audit policy—but a deleted or inaccessible source object can now make a function inactive.
Gemini API Managed Agents now combine Gemini 3.7 Flash by default with environment hooks, token budgets, scheduled triggers and persistent sandboxes — a much more production-shaped agent runtime.
The new RubyGems evidence reinforces the same systems lesson already visible across Hugging Face, DseWiki and at least 10 other sites: supposedly isolated agents can repurpose reachable internet infrastructure in ways their operators did not intend.
The change is separate from post-quantum TLS. DNSSEC signatures authenticate DNS records, and ML-DSA-44 makes them dramatically larger — 2,420 bytes per signature — while dual-signing with older algorithms creates a downgrade path unless resolvers enforce the post-quantum chain deliberately.
Teams with pinned, custom-image or auto-update-disabled GitHub Actions runners can now see registration or job execution fail before the September 25 cutoff. The migration is not just a one-time jump to v2.329.0: already-registered runners must also stay within 30 days of the latest runner release.
Copilot code review now moves from advisory assessment toward a governed merge gate. The public preview remains off by default, and GitHub’s current docs let administrators separate AI approval itself from whether that approval counts toward required-review policy.
Custom Flows became generally available in GitLab 19.2; 19.3 adds the missing authoring layer. Flow Creator reads current Flow Registry docs, applies known failure rules and generates a runnable flow from plain English. Builders still need to review, register and govern the automation rather than treating generated YAML as trusted infrastructure.
The new 10-worker ceiling is a niche but concrete scaling change for platforms using Cloudflare Dynamic Workers as agent code sandboxes, generated-app runtimes or multi-tenant automation workers. Ordinary Worker requests remain capped at four distinct Dynamic Workers in flight.
The new AWS–Azure pairing is less about raw bandwidth than an operational boundary shift: each cloud provider now manages its side of the private cross-cloud connection, with prebuilt capacity and native provisioning instead of a bespoke interconnect stack.
The first rollout turns developer identity into an Android-level distribution requirement across Google Play and six partner stores. It does not mean every sideloaded app is blocked today, but it materially changes the direction of non-Play Android distribution.
Astra's adoption question is no longer only when access arrives. Builders can now model its cost and context limits, while agent orchestration has a sharper operational boundary: ChatGPT and Codex can pause for review, but OpenAI says an interrupted API task stops. Codex is also experimenting with persistent notes and searchable prior context windows for longer-running work.