Operations | Monitoring | ITSM | DevOps | Cloud

Miasma has already hit Red Hat and 73 Microsoft GitHub repos. Here's how it works and what your team can do right now. Nigel Douglas, Head of Developer Relations at Cloudsmith, breaks down the Miasma worm – a self-replicating supply chain attack and evolved variant of Mini Shai-Hulud from threat group TeamPCP. Learn how Miasma uses the yo-yo attack method to move laterally across registries and workstations, why conventional scanners missed it, and the practical steps security teams can take today, including cooldown policies and continuous risk assessment.

Catch failing tests before they ever leave the machine with just two hooks and Chunk sidecars.

"The biggest surprise was how much support we've gotten from the Control Plane team." — Minga Most teams know the drill: unless you're paying a lot, you don't get real support from GCP or AWS. Minga found the opposite with Control Plane. Whenever an infrastructure issue comes up, the Control Plane team jumps in — digging through logs, tracking down the root cause, and staying in the trenches even when the problem isn't theirs to fix.

Bitbucket Pipelines already supports triggering on repository pushes and pull request pushes. But if you wanted to react to other events like a deployment finishing, a build failing, or a PR getting merged, you had to wire that up yourself with webhooks or external glue code. New trigger types let you define those conditions directly in your YAML. You can fire custom pipelines on events like pipeline-completed, deployment-completed, pullrequest-created, pullrequest-fulfilled, and more.