Today we are releasing versions 10.0.4, 9.5.9, and 9.4.7 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain several security fixes, including fixes for two persistent Cross-Site Scripting (XSS) vulnerabilities, an open redirect vulnerability, a bug when changing usernames that could leave behind and leak repositories, an information leakage vulnerability in private issue names, and security updates for Ruby and libxml2. We recommend that all GitLab installations be upgraded to one of these versions.
Please read on for more details.
Development issues can be expensive to fix — and the later you uncover them, the worse it is. If you’re running (or dependent on) a development project it’s really important that you stay on the ball at all times. Communication, transparency, and accountability are all essential. Here are some development project red flags that you need to be aware of – as well as how you can address things if it looks like they are starting to go wrong…
Tech-savvy educators! Do you want to:
Today we are thrilled to announce our $20 million Series C funding led by GV. This follows our Series B round last September. With the help of our investors (and community!) we’re gearing up to bring you Complete DevOps, a reimagined scope of DevOps that unifies development and operations work into a single user experience.
With GitLab 10.0, we shipped Auto DevOps for the Community and Enterprise Editions. Read on for an in-depth look at our strategy behind it, and beyond.
Today we are releasing version 9.5.8 for GitLab Community Edition (CE) and Enterprise Edition (EE).
This version includes backports of fixes for bugs that are present in the 9.5.x releases.
Today we are releasing version 9.5.7 for GitLab Community Edition (CE) and Enterprise Edition (EE).
This version resolves a single regression introduced in 9.5.4, which prevented admins from importing repositories from the command line.
For a long time GitLab.com used a single PostgreSQL database server and a single replica for disaster recovery purposes. This worked reasonably well for the first few years of GitLab.com's existence, but over time we began seeing more and more problems with this setup. In this article we'll take a look at what we did to help solve these problems for both GitLab.com and self-hosted GitLab instances.