sarki_247

(GitLab Team member here) You can learn more about the disclosure from GitLab, the security releases made and the recommended actions at https://about.gitlab.com/releases/2024/01/11/critical-securi...

> "It would make sense if they had a "newest only", where if you have one deployment running and 10 pending, by the time the current deployment finishes, gitlab would cancel all deployments except for the latest one. This way you don't have to wait for old deployments, and you're free to do a rollback at any time."

Hi, GitLab Team member here. This is exactly how GitLab functions when you use "newest first" process mode [1] with Prevent outdated deployment jobs enabled [2]. By default, pipeline job retries for deployment rollback is enabled, you can rollback to any of the failed old deployments, except where its disabled. [3]

[1] https://docs.gitlab.com/ee/ci/resource_groups/#process-modes

[2] https://docs.gitlab.com/ee/ci/environments/deployment_safety...

[3] https://docs.gitlab.com/ee/ci/environments/deployment_safety...

GitLab team member here. With GitLab Ultimate, users with the guest role do not consume a seat. To learn more, see https://docs.gitlab.com/ee/subscriptions/self_managed/index....

Hi, GitLab team member here. We offer the Open Source program for qualifying projects giving them access to top-tier features for free. See https://about.gitlab.com/solutions/open-source/join/

GitLab team member here! This feature is currently being worked on. You can follow the progress in https://gitlab.com/gitlab-org/gitlab-web-ide/-/issues/72

GitLab team member here. No, it's not. This service will not be replacing our self-hosted versions.

GitLab team member here! User Limits will not apply to a public group as a top namespace and as at this time, no limit on private groups within a public top namespace group. See the 6th Q&A entry in the FAQ page (https://about.gitlab.com/pricing/faq-efficient-free-tier/#us...), excerpt here:

> Q. Do these changes apply to private projects within a top-level namespace with public visibility? A. User limits are currently applied based on the visibility of the top-level namespace. We will monitor how top-level namespaces with public visibility are using private projects to identify whether any limits on such projects are needed.

Hi, GitLab team member here. Due to a number of factors, which includes high applicant volumes, the talent acquisition team may not be able to provide detailed decline feedback. You can get more details on our handbook page: https://about.gitlab.com/handbook/hiring/interviewing/#rejec...

A minor correction above, the last phrase is supposed to read "why we prioritized annual over monthly pricing", as described on the linked GitLab handbook page.

GitLab team member here, Our pricing model page (https://about.gitlab.com/company/pricing/#annual-pricing-is-...) details our pricing strategy and why we prioritized monthly over annual pricing.

GitLab team member here! This implementation will be client-side only, with a selection of extensions allowed. Self-hosted instance admins will be able to enable or create an allow-list of extensions on their instance. You can learn more in this epic: https://gitlab.com/groups/gitlab-org/-/epics/7683

GitLab Team member here! You can set up different environments with whatever dependency your application needs. GitLab CI can build/deploy your application to the right environment depending on various factors. You can also look at GitLab Review Apps, which "is a collaboration tool that assists with providing an environment to showcase product changes."

See: https://docs.gitlab.com/ee/ci/review_apps/

GitLab team member here, most of the affected relationships have been restored. If you are still affected, please let us know in the incident issue: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/6...