cherry pick

Images are almost always the heaviest thing on a web page. A single hero photo can weigh more than all the HTML, CSS and JavaScript of a site put together, and every extra kilobyte delays the moment a visitor finally sees something useful. Search engines notice it, and users on mobile data notice it faster. The encouraging part is that image delivery is one of the few areas where the fixes are well documented, mostly automatable, and visible in the metrics almost immediately.

Within a single day, several unrelated security problems came to light and kept security teams occupied. PHP disclosed two critical remote code execution flaws, Node.js released a security update fixing four high-severity issues, a malicious LiteLLM version showed up in public package and container registries, and an Indian certificate authority was found to have eight intermediate keys that anyone could guess. Every one of these problems affects a different layer of the stack, and seeing them together shows how many points of exposure a single server or container image can have at once.

Git is a widely used version control system, and its commands cover everything from saving a single change to rewriting the history of an entire repository. Each command acts on a specific part of the repository, and choosing one without knowing what it changes can rewrite shared history or discard work that was never saved anywhere else.