|
| 1 | +- name: Customize compliance frameworks with requirements and compliance controls |
| 2 | + description: | # Do not modify this line, instead modify the lines below. |
| 3 | + Previously, compliance frameworks in GitLab could be created as a label to identify that your project has certain compliance requirements or needs additional oversight. This label could then be used as a scoping mechanism to ensure that security policies could be enforced on all projects within a group. In this release, we are introducing a new way for compliance managers to get more in-depth compliance monitoring in GitLab through 'requirements'. With requirements, as part of a custom compliance framework, you can define specific requirements from a number of different compliance standards, laws, and regulations that must be followed as an organization. We are also expanding the number of compliance controls (previously known as compliance checks) that we offer from five to over 50! These 50 out-of-the-box (OOTB) controls can be mapped to the compliance framework requirements. These controls check particular project, security, and merge request settings across your GitLab instance to help you meet requirements under a number of different compliance standards, laws, and regulations such as SOC2, NIST, ISO 27001, and the GitLab CIS Benchmark. Adherence to these controls is reflected in standard adherence report, which is redesigned to take into account requirements and the mapping of controls to those requirements. In addition to expanding our OOTB controls, we now allow users to map requirements to external controls, which can be for items, programs, or systems that exist outside the GitLab platform. These mappings allow you to use the GitLab compliance centre as the single source of truth when it comes to your compliance monitoring and audit evidence needs. |
| 4 | + stage: software_supply_chain_security |
| 5 | + self-managed: true |
| 6 | + gitlab-com: true |
| 7 | + available_in: [Ultimate] |
| 8 | + documentation_link: https://docs.gitlab.com/user/compliance/compliance_center/compliance_status_report |
| 9 | + image_url: https://about.gitlab.com/images/17_11/custom_compliance_frameworks.png |
| 10 | + published_at: 2025-04-17 |
| 11 | + release: 17.11 |
| 12 | +- name: More AI features on GitLab Duo Self-Hosted |
| 13 | + description: | # Do not modify this line, instead modify the lines below. |
| 14 | + You can now use more [GitLab Duo](https://about.gitlab.com/gitlab-duo/) features with GitLab Duo Self-Hosted in your GitLab Self-Managed instance. The following features are available in beta: |
| 15 | +
|
| 16 | + - [Root Cause Analysis](https://docs.gitlab.com/user/gitlab_duo_chat/examples/#troubleshoot-failed-cicd-jobs-with-root-cause-analysis) |
| 17 | + - [Vulnerability Explanation](https://docs.gitlab.com/user/application_security/vulnerabilities/#explaining-a-vulnerability) |
| 18 | + - [Vulnerability Resolution](https://docs.gitlab.com/user/application_security/vulnerabilities/#vulnerability-resolution) |
| 19 | + - [AI Impact Dashboard](https://docs.gitlab.com/user/analytics/ai_impact_analytics/) |
| 20 | + - [Discussion Summary](https://docs.gitlab.com/user/discussions/#summarize-issue-discussions-with-duo-chat) |
| 21 | + - [Merge Request Commit Message](https://docs.gitlab.com/user/project/merge_requests/duo_in_merge_requests/#generate-a-merge-commit-message) |
| 22 | + - [Merge Request Summary](https://docs.gitlab.com/user/project/merge_requests/duo_in_merge_requests/#generate-a-description-by-summarizing-code-changes) |
| 23 | + - [GitLab Duo for the CLI](https://docs.gitlab.com/editor_extensions/gitlab_cli/#gitlab-duo-for-the-cli) |
| 24 | +
|
| 25 | + [Code Review Summary](https://docs.gitlab.com/user/project/merge_requests/duo_in_merge_requests/#summarize-a-code-review) is also available on GitLab Duo Self-Hosted as an experiment. |
| 26 | + stage: ai-powered |
| 27 | + self-managed: true |
| 28 | + gitlab-com: false |
| 29 | + available_in: [Ultimate] |
| 30 | + documentation_link: https://docs.gitlab.com/administration/gitlab_duo_self_hosted/#supported-gitlab-duo-features |
| 31 | + image_url: https://about.gitlab.com/images/17_11/ResizedExpandedDuoFeaturesImage.jpg |
| 32 | + published_at: 2025-04-17 |
| 33 | + release: 17.11 |
| 34 | +- name: Epic, issue, and task custom fields |
| 35 | + description: | # Do not modify this line, instead modify the lines below. |
| 36 | + With this release, you can configure text, number, single-select, and multi-select custom fields for issues, epics, tasks, objectives, and key results. While labels have been the primary way to categorize work items up to this point, custom fields provide a more user-friendly approach for adding structured metadata to your planning artifacts. |
| 37 | +
|
| 38 | + Custom fields are configured in your top-level group and cascade to all subgroups and projects. You can map fields to one or more work item types and filter by custom field values in the issues and epics lists. |
| 39 | + stage: plan |
| 40 | + self-managed: true |
| 41 | + gitlab-com: true |
| 42 | + available_in: [Ultimate] |
| 43 | + documentation_link: https://docs.gitlab.com/user/work_items/custom_fields |
| 44 | + image_url: https://about.gitlab.com/images/17_11/work-items-custom-fields.png |
| 45 | + published_at: 2025-04-17 |
| 46 | + release: 17.11 |
| 47 | +- name: CI/CD pipeline inputs |
| 48 | + description: | # Do not modify this line, instead modify the lines below. |
| 49 | + CI/CD variables are essential for dynamic CI/CD workflows, and are used for many things, including as environment variables, context variables, tool configuration, and matrix variables. But developers sometimes rely on CI/CD variables to inject [pipeline variables](https://docs.gitlab.com/ci/variables/#use-pipeline-variables) into pipelines to manually modify pipeline behavior, which have some risks due to the higher precedence of pipeline variables. |
| 50 | +
|
| 51 | + In GitLab 17.11 and later, you can now use `inputs` to safely modify pipeline behavior instead of using pipeline variables, including in scheduled pipelines, downstream pipelines, triggered pipelines, and other cases. Inputs provide developers with a more structured and flexible solution for injecting dynamic content at CI/CD job runtime. After you switch to inputs, you can completely [disable access to pipeline variables](https://docs.gitlab.com/ci/variables/#restrict-pipeline-variables). |
| 52 | + stage: verify |
| 53 | + self-managed: true |
| 54 | + gitlab-com: true |
| 55 | + available_in: [Ultimate] |
| 56 | + documentation_link: https://docs.gitlab.com/ci/inputs/#for-a-pipeline |
| 57 | + image_url: https://about.gitlab.com/images/17_11/run_new_pipeline_spec_input.png |
| 58 | + published_at: 2025-04-17 |
| 59 | + release: 17.11 |
0 commit comments