At the beginning of 2020, none of us could have imagined what we would be talking and thinking about at the end of the year. At JFrog, we began by talking about unifying everything in the DevOps lifecycle. Of course very quickly, the message of unity and togetherness would soon become even bigger than we could imagine in light of the global pandemic.

In 2020, JFrog’s experts published a treasure trove of content — blogs, articles, infographics, and more — to share insights and advice with our customers and the DevOps community at large. In case you missed them — or want to re-read them — here’s a list of the most popular ones. They range from a primer on container registries to an explainer on achieving high-availability for your Maven repository.

How many major versions of a given Go module are there? That simple question doesn’t always have an easy-to-discover answer. Golang’s unique system of semantic import versioning solves some key problems of ensuring Go module compatibility across dependencies. But it also makes it a bit harder to learn what major versions of a Go module are available. The go client doesn’t provide a way to find out, nor will it inform you when a newer major version of a dependency exists.

The SolarWinds hack, which has affected high-profile Fortune 500 companies and large U.S. federal government agencies, has put the spotlight on software development security — a critical issue for the DevOps community and for JFrog. At a fundamental level, if the code released via CI/CD pipelines is unsafe, all other DevOps benefits are for naught.

We get it, installing Artifactory and the JFrog DevOps Platform on Kubernetes can be daunting. As easy as we’ve sought to make it with our official JFrog installation Helm charts, there are a lot of decisions to be made. That’s meant to give you the widest possible choice for how to best fit your JFrog installation to your infrastructure. But choice can be overwhelming, too.