GitLab pushes out 11.1, then patches it, as it clears decks for Google Cloud leap

GitLab pushes out 11.1, then patches it, as it clears decks for Google Cloud leap
Gitlab Logo

GitLab pushed out version 11.1 of its platform, then promptly followed it up with a patch, just days before it embarks on its migration from longtime home Azure to Google Cloud Platform.

The firm is highlighting the security benefits of its latest iteration, with a new Security Dashboard, which it promises will give visibility into “how all security issues are affecting a branch in aggregate” rather than forcing users to collate reports across Merge Requests. The dashboard can be used to dismiss false positives or to create issues to solve existing vulnerabilities, it said.

The other main highlight is enhanced search in GitLab, which now allows filtering by filename, path and extension. Other changes include the addition of Container Scanning and DAST to its list of security reports, adding Node.js to its roster of supported SAST languages, and a raft of UI changes. The full list of changes is available here.

However, GitLab almost immediately issued a patch – bringing us up to 11.1.1 – to deal with “a number of regressions and bugs in this month’s 11.1 release and prior versions.”

Security is clearly top of mind for GitLab at the moment. Last week it released a rake of security fixes to address vulnerabilities in its 11.0.4, 10.8.6, and 10.7.7. Community and Enterprise Editions. The details of the vulns will be made publicly available in about three weeks.

Meanwhile, GitLab will be performing its migration from Azure to Google Cloud Platform this coming weekend.

The firm said, “While Azure has been a great provider for us, GCP has the best Kubernetes support and we believe will the best provider for our long-term plans.” GitLab said it would reap “significant gains” from running natively on Kubernetes. None of this should necessarily be a surprise – Kubernetes sprung into life as a Google project afterall.

Immediate benefits for customers would include “encrypted data at rest on by default and faster caching due to GCP’s tight integration with our existing CDN,” said GitLab.

Funnily enough, it didn’t mention the imminent borging of rival Git-co GitHub by one Microsoft of Redmond, Washington.

In the meantime, the change-over is due to kickoff at 10:00 UTC on Saturday, July 27, and due to last two hours. During this time, a number of services will be unavailable: the SaaS website; Git ssh; Git https; registry; and CI/CD.