NPM Registry now supports authentication with the GitLab Personal Access Token CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD The GitLab NPM Registry allows Javascript developers to build, publish, and version NPM packages using their GitLab instance. NPM requires users to authenticate with OAuth and prior to 12.2, the GitLab personal access token did not support OAuth. Users were forced to generate their own token (outside of GitLab) in order to use the NPM registry, which also prevented them from leveraging two-factor authentication. This was not a scalable solution for our enterprise customers. In 12.2 we are excited to announce that we now support authentication using the GitLab personal access token. The GitLab personal access token works seamlessly with two-factor authentication and allows users to choose a scope and expiration policy that works for them. Simply update your .nprmrc file with your personal access token and begin publishing and downloading packages to the GitLab NPM Registry. Documentation Issue

Maintainers can create subgroups CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD For large organizations prioritizing agility, subgroups are a valuable tool for keeping an instance organized as it continues to scale. We’re now providing the option for group Owners to grant Maintainers the ability to create subgroups. With this option enabled, Maintainers in a group will be able to move independently and quickly, without requiring intervention from group Owners to keep their projects organized. Thanks to Fabio Papa for the contribution! Documentation Issue

Improved diff expansion CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD When viewing a diff, most unchanged lines are hidden so that it is easy to quickly read the changes. But sometimes more context is needed. In GitLab 12.2, hidden line ranges can now be revealed in full or incrementally. Previously hidden line ranges could only be revealed incrementally from the bottom of the range. Documentation Issue

Assign groups as code owners CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Knowing who should review your changes often isn’t obvious. Assigning code owners to files makes this easy. Once assigned, you can see code owners when viewing a file and automatically add them as merge request approvers. In GitLab 12.2, you can now assign Groups, in addition to a GitLab username and email as code owners. Assigning a group prevents code owners falling out of sync as teams change, particularly when using LDAP to manage group membership. Documentation Issue

Design Management uploads CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Designers and Developers can now easily collaborate on design assets inside of a GitLab issue with GitLab’s Design Management uploads. Designs can be uploaded to a new area inside of an issue for easy tracking and collaboration. Documentation Issue

Multi-select delete for the Container Registry CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Practicing proper container registry hygiene is important. Over time, images can accumulate and take up a significant amount of disk space. Additionally, too many tags can significantly slow down the load time of the container registry management page at Packages > Container Registry making it difficult to use. Previously, there have been a few options for maintaining your registry, each with their own challenges. You could use the bulk tag delete API and garbage collection to automate clean up, but this requires you to write and maintain a script. You could also manually delete images and tags from the management page, but this is very time-consuming as each image tag needed to be deleted one at a time. Now, we’ve updated and improved the GitLab UI to make manual pruning significantly faster. You can select multiple tags at a time and selecting an image will automatically select all of the associated tags. This should make it easier to maintain your registry, lowering your storage costs, and keeping page performance snappy. We’re happy to release this iteration of the container registry and have more improvements on the way. Be on the lookout for future improvements such as the ability to set policy for retention and expiration. Documentation Issue

Kubernetes namespace for each environment CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Using the same Kubernetes cluster for multiple environments can net you some great efficiencies. For example, if dev and stage both use the same cluster, then administrative overhead goes down because you only have one cluster to manage, and infrastructure cost goes down because Kubernetes can schedule pods from both environments onto a smaller set of nodes. Previously, GitLab didn’t support this use case well, all environments in a project were deployed into the same namespace. If you wanted separate permissions for each environment (for example, if you wanted to allow engineering to deploy to dev but not stage) you needed to use a separate cluster for each. The GitLab Kubernetes integration now uses a dedicated namespace for each project environment, and you can finely configure permissions separately for each so you can take advantage of the efficiencies that come with using the same cluster for multiple environments. This will allow Kubernetes users to reuse the same cluster for different environments without having to deploy all environments into the same namespace. Additionally, operators are now able to finely configure permissions for each environment to allow users to deploy to some but not all environments. Documentation Issue

Uninstall Helm from Kubernetes GitLab Managed Apps CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD If you installed Helm to your Kubernetes cluster via the GitLab Kubernetes integration, you can now also uninstall it with a single click from the cluster page. Documentation Issue

Disable Group Or Project Email Notifications CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Owners can now disable email notifications at the Group or Project level, regardless of individual user settings. If this is activated on a group level, it will cascade down to all sub-groups and projects within the parent group. Documentation Issue

Lockfile to prevent multiple runner instances on a single host CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Running multiple instances of the gitlab-runner process on a single host can cause some extremely confusing and hard to debug behaviors. Since this is not the intended usage, we’ve introduced a lockfile that will prevent this from accidentally occurring. Documentation Issue

Improved variable masking for `@` and `:` characters CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD We have added support for two additional characters in variable masking, improving the ability for GitLab to automatically hide more, different kinds of secrets than it is able to today. Documentation Issue

Label issues opened by Prometheus alerts with incident CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD When you have configured your project to open issues on Prometheus alerts, the incident label will now be applied automatically. This enables incident response teams to easily triage incidents using issue boards and eliminates manual work required to indicate issues that are incidents and those being used for other purposes. Documentation Issue

Read and write admin notes for a user via API CORE STARTER PREMIUM ULTIMATE FREE BRONZE SILVER GOLD Writing admin notes for users can be a useful tool for administrating a GitLab userbase at scale. On GitLab.com, our admins typically use the note attribute to keep track of user behavior. At scale, writing these notes via the UI quickly becomes challenging to manage. The user API can now be used to read and write admin notes, making it easier than ever for instance admins to add reminders at the user level. Documentation Issue