You can compare GitLab with the more famous GitHubbut contains some subtle differences† It is an environment for managing Git repositories on-premises and is released under the MIT Expat license and developed in Ruby on Rails. It is available in two versions, namely the free-to-use Community Edition and a paid Enterprise Edition, with more features aimed at large businesses. The two flavors are on this page explained. The development team has released updates for GitLab versions 14.3, 14.4, and 14.5, which address several security vulnerabilities.
GitLab Security Release: 14.5.2, 14.4.4, and 14.3.6
Today we are releasing versions 14.5.2, 14.4.4, and 14.3.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version.
GitLab releases patches for vulnerabilities in dedicated security releases. There are two types of security releases: a monthly, scheduled security release, released a week after the feature release (which deploys on the 22nd of each month), and ad-hoc security releases for critical vulnerabilities. For more information, you can visit our security FAQ† You can see all of our regular and security release blog posts here† In addition, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched.
We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is highly recommended that all customers upgrade to the latest security release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.
|Version number||14.5.2, 14.4.4, and 14.3.6|
|License type||Conditions (GNU/BSD/etc.)|