diff options
Diffstat (limited to 'data')
11 files changed, 196 insertions, 9 deletions
diff --git a/data/deprecations/15-3-omniauth-crowd.yml b/data/deprecations/15-3-omniauth-crowd.yml index 7c28226a674..2230bbd17ed 100644 --- a/data/deprecations/15-3-omniauth-crowd.yml +++ b/data/deprecations/15-3-omniauth-crowd.yml @@ -3,13 +3,13 @@ # - title: "Atlassian Crowd OmniAuth provider" # (required) The name of the feature to be deprecated announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + removal_milestone: "18.0" # (required) The milestone when this feature is planned to be removed breaking_change: true # (required) If this deprecation is a breaking change, set this value to true reporter: hsutor # (required) GitLab username of the person reporting the deprecation stage: Manage # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/369117 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. The `omniauth_crowd` gem that provides GitLab with the Atlassian Crowd OmniAuth provider will be removed in our - next major release, GitLab 16.0. This gem sees very little use and its + next major release, GitLab 18.0. This gem sees very little use and its [lack of compatibility](https://github.com/robdimarco/omniauth_crowd/issues/37) with OmniAuth 2.0 is [blocking our upgrade](https://gitlab.com/gitlab-org/gitlab/-/issues/30073). diff --git a/data/deprecations/15-8-deprecate-slack-notifications-integration.yml b/data/deprecations/15-8-deprecate-slack-notifications-integration.yml index 33f9e6ce3a7..21c6cb7d0cf 100644 --- a/data/deprecations/15-8-deprecate-slack-notifications-integration.yml +++ b/data/deprecations/15-8-deprecate-slack-notifications-integration.yml @@ -1,17 +1,16 @@ - title: "Slack notifications integration" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + removal_milestone: "18.0" # (required) The milestone when this feature is planned to be removed breaking_change: true # (required) Change to false if this is not a breaking change. reporter: g.hickman # (required) GitLab username of the person reporting the change stage: manage # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/372411 # (required) Link to the deprecation issue in GitLab + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/435909 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. As we're consolidating all Slack capabilities into the - GitLab for Slack app, we're [deprecating the Slack notifications - integration](https://gitlab.com/gitlab-org/gitlab/-/issues/372411). - GitLab.com users can now use the GitLab for Slack app to manage notifications - to their Slack workspace. For self-managed users of the Slack notifications integration, - we'll be introducing support in [this epic](https://gitlab.com/groups/gitlab-org/-/epics/1211). + GitLab for Slack app, we've deprecated the Slack notifications + integration. + Use the GitLab for Slack app to manage notifications + to your Slack workspace. # # OPTIONAL END OF SUPPORT FIELDS diff --git a/data/deprecations/16-7-remove-slsa-0.2-statement.yml b/data/deprecations/16-7-remove-slsa-0.2-statement.yml new file mode 100644 index 00000000000..745036d2ecc --- /dev/null +++ b/data/deprecations/16-7-remove-slsa-0.2-statement.yml @@ -0,0 +1,12 @@ +# +# REQUIRED FIELDS +# +- title: "GitLab Runner provenance metadata SLSA v0.2 statement" + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + announcement_milestone: "16.8" # (required) The milestone when this feature was first announced as deprecated. + breaking_change: true # (required) Change to false if this is not a breaking change. + reporter: sam.white # (required) GitLab username of the person reporting the change + stage: verify # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/36869 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + Runners generate provenance metadata and currently defaults to generating statements that adhere to SLSA v0.2. Because SLSA v1.0 has been released and is now supported by GitLab, the v0.2 statement is now deprecated and removal is planned in GitLab 17.0. The SLSA v1.0 statement is planned to become the new default statement format in GitLab 17.0. diff --git a/data/deprecations/16-8-api-lint-ref-removal.yml b/data/deprecations/16-8-api-lint-ref-removal.yml new file mode 100644 index 00000000000..cd99938a607 --- /dev/null +++ b/data/deprecations/16-8-api-lint-ref-removal.yml @@ -0,0 +1,34 @@ +# ----- DELETE EVERYTHING ABOVE THIS LINE ----- + +- title: "Block usage of ref and sha together in `GET /projects/:id/ci/lint`" + # The milestones for the deprecation announcement, and the removal. + removal_milestone: "17.0" + announcement_milestone: "16.8" + # Change breaking_change to false if needed. + breaking_change: true + # The stage and GitLab username of the person reporting the change, + # and a link to the deprecation issue + reporter: dhershkovitch + stage: verify + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/430322 + body: | # (required) Don't change this line. + Due to a problem with ambiguity, we've deprecated the use of both `ref` and `sha` in the same API call to `GET /projects/:id/ci/lint`. Make sure your API calls to this endpoint use only `ref` or `sha`, but not both. In GitLab 17.0, using them in the same call will no longer be possible to ensure the correct ref or SHA is linted. + +# ============================== +# OPTIONAL END-OF-SUPPORT FIELDS +# ============================== +# +# If an End of Support period applies: +# 1) Share this announcement in the `#spt_managers` Support channel in Slack +# 2) Mention `@gitlab-com/support` in this merge request. +# + # When support for this feature ends, in XX.YY milestone format. + end_of_support_milestone: + # Array of tiers the feature is currently available to, + # like [Free, Silver, Gold, Core, Premium, Ultimate] + tiers: + # Links to documentation and thumbnail image + documentation_url: + image_url: + # Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg + video_url: diff --git a/data/deprecations/16-8-deprecate-license-list.yml b/data/deprecations/16-8-deprecate-license-list.yml new file mode 100644 index 00000000000..a5955c60361 --- /dev/null +++ b/data/deprecations/16-8-deprecate-license-list.yml @@ -0,0 +1,16 @@ +- title: "License List is deprecated" + removal_milestone: "17.0" + announcement_milestone: "16.8" + breaking_change: true + reporter: abellucci + stage: govern + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/436100 + body: | # (required) Don't change this line. + Today in GitLab you can see a list of all of the licenses your project and the components that + use that license on the License List. As of 16.8, the License List + is deprecated and scheduled to be removed in 17.0 as a breaking change. + With the release of the [Group Dependency List](https://docs.gitlab.com/ee/user/application_security/dependency_list/) + and the ability to filter by license on the project and group Dependency List, you can now + access all of the licenses your project or group is using on the Dependency List. + tiers: [Gold, Ultimate] + documentation_url: https://docs.gitlab.com/ee/user/compliance/license_list.html diff --git a/data/deprecations/16-8-deprecate-pg_schema-backup-setting.yml b/data/deprecations/16-8-deprecate-pg_schema-backup-setting.yml new file mode 100644 index 00000000000..4edb2c8fde2 --- /dev/null +++ b/data/deprecations/16-8-deprecate-pg_schema-backup-setting.yml @@ -0,0 +1,14 @@ +- title: "Support for setting custom schema for backup is deprecated" + announcement_milestone: "16.8" + removal_milestone: "17.0" + breaking_change: true + reporter: sranasinghe + stage: core platform + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/435210 + body: | + You could configure GitLab to use a custom schema for backup, by setting + `gitlab_rails['backup_pg_schema'] = '<schema_name>'` in `/etc/gitlab/gitlab.rb` for Linux package installations, + or by editing `config/gitlab.yml` for self-compiled installations. + + While the configuration setting was available, it had no effect and did not serve the purpose it was intended. + This configuration setting will be removed in GitLab 17.0. diff --git a/data/deprecations/16-8-license-scanning-sbt-1-0-x.yml b/data/deprecations/16-8-license-scanning-sbt-1-0-x.yml new file mode 100644 index 00000000000..232fe87de0a --- /dev/null +++ b/data/deprecations/16-8-license-scanning-sbt-1-0-x.yml @@ -0,0 +1,11 @@ +- title: "License Scanning support for sbt 1.0.X" + removal_milestone: "17.0" + announcement_milestone: "16.8" + breaking_change: true + reporter: thiagocsf + stage: Secure + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/437591 + body: | # (required) Don't change this line. + GitLab 17.0 removes License Scanning support for sbt 1.0.x. + + Users are advised to upgrade from sbt 1.0.x. diff --git a/data/deprecations/16-8-remove-deprecated-metric-filter-from-dora-api.yml b/data/deprecations/16-8-remove-deprecated-metric-filter-from-dora-api.yml new file mode 100644 index 00000000000..75a49e9b175 --- /dev/null +++ b/data/deprecations/16-8-remove-deprecated-metric-filter-from-dora-api.yml @@ -0,0 +1,9 @@ +- title: "`metric` filter and `value` field for DORA API" + announcement_milestone: "16.8" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + breaking_change: true # (required) If this deprecation is a breaking change, set this value to true + reporter: hsnir1 # (required) GitLab username of the person reporting the deprecation + stage: plan # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/393172 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + Multiple DORA metrics can now be queried simultaneously using a new metrics field. The `metric` filter and `value` field for Graphql DORA API will be removed in GitLab 17.0. diff --git a/data/deprecations/16-9-verify-after-script-canceled-status.yml b/data/deprecations/16-9-verify-after-script-canceled-status.yml new file mode 100644 index 00000000000..c34ee4337af --- /dev/null +++ b/data/deprecations/16-9-verify-after-script-canceled-status.yml @@ -0,0 +1,13 @@ +- title: "`after_script` keyword will run for cancelled jobs" + # The milestones for the deprecation announcement, and the removal. + removal_milestone: "17.0" + announcement_milestone: "16.8" + # Change breaking_change to false if needed. + breaking_change: true + # The stage and GitLab username of the person reporting the change, + # and a link to the deprecation issue + reporter: jreporter + stage: verify + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/437789 + body: | # (required) Don't change this line. + The [`after_script`](https://docs.gitlab.com/ee/ci/yaml/#after_script) CI/CD keyword is used to run additional commands after the main `script` section of a job. This is often used for cleaning up environments or other resources that were used by the job. For many users, the fact that the `after_script` commands do not run if a job is cancelled was unexpected and undesired. In 17.0, the keyword will be updated to also run commands after job cancellation. Make sure that your CI/CD configuration that uses the `after_script` keyword is able to handle running for cancelled jobs as well. diff --git a/data/deprecations/17-0-dependency-scanning-sbt-support.yml b/data/deprecations/17-0-dependency-scanning-sbt-support.yml new file mode 100644 index 00000000000..a255cd9585e --- /dev/null +++ b/data/deprecations/17-0-dependency-scanning-sbt-support.yml @@ -0,0 +1,11 @@ +- title: "Dependency Scanning support for sbt 1.0.X" + removal_milestone: "17.0" + announcement_milestone: "16.8" + breaking_change: true + reporter: johncrowley + stage: Secure + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/415835 + body: | # (required) Don't change this line. + Supporting very old versions of sbt is preventing us from improving our support for additional use cases with this package manager without increasing our maintenance cost. + + Version 1.1.0 of sbt was released 6 years ago, and users are advised to upgrade from 1.0.x as Dependency Scanning will no longer work. diff --git a/data/whats_new/202312210001_16_7.yml b/data/whats_new/202312210001_16_7.yml new file mode 100644 index 00000000000..093899cddbf --- /dev/null +++ b/data/whats_new/202312210001_16_7.yml @@ -0,0 +1,68 @@ +- name: GitLab Duo Code Suggestions is generally available + description: | # Do not modify this line, instead modify the lines below. + [GitLab Duo Code Suggestions](https://about.gitlab.com/solutions/code-suggestions/) is now generally available! + + GitLab Duo Code Suggestions helps teams create software faster and more efficiently, by completing lines of code and defining and generating logic for functions. + + Code Suggestions is built with privacy as a critical foundation. Private, non-public customer code stored in GitLab is not used as training data. Learn about [data usage](https://docs.gitlab.com/ee/user/project/repository/code_suggestions/index.html#code-suggestions-data-usage) when using Code Suggestions. + + In the general release, we've made [Code Suggestions available across several IDEs](https://docs.gitlab.com/ee/user/project/repository/code_suggestions/#supported-editor-extensions). Code Suggestions is also now more intuitive and responsive. + + GitLab Duo Code Suggestions is [free to try](https://docs.gitlab.com/ee/user/project/repository/code_suggestions/#start-using-code-suggestions) subject to the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/) until February 15, 2024. Starting today, you can buy Code Suggestions as an add-on to GitLab subscriptions for an introductory price of $9 USD per user/per month. Please [contact us](https://about.gitlab.com/solutions/code-suggestions/) to get started with Code Suggestions. + stage: Create + self-managed: true + gitlab-com: true + available_in: [Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/user/project/repository/code_suggestions/ + image_url: https://img.youtube.com/vi/hCAyCTacdAQ/hqdefault.jpg + published_at: 2023-12-21 + release: 16.7 + +- name: New drill-down view from Insights report charts + description: | # Do not modify this line, instead modify the lines below. + With the Insights report you can analyze patterns over time using customizable charts. The new drill-down capability added to the “Bugs created by priority” and “Bugs created by severity” Insights reports allows you to drill down on the Issue analytics report for deeper analysis. + + We plan to include this capability in the other Insight reports as a custom option in a later version. + stage: Plan + self-managed: true + gitlab-com: true + available_in: [Ultimate] + documentation_link: https://docs.gitlab.com/ee/user/group/insights/#drill-down-on-charts + image_url: https://about.gitlab.com/images/16_7/insights_drill_16_7.gif + published_at: 2023-12-21 + release: 16.7 + +- name: SAST results in MR changes view + description: | # Do not modify this line, instead modify the lines below. + SAST findings now appear in the merge request Changes view. + This makes it easier to see, understand, and fix potential weaknesses during the code review process. + + Lines containing SAST issues are marked by a symbol beside the gutter. + Select the symbol to see the list of issues, then select an issue to see its details. + + We've enabled this feature on GitLab.com. + We plan to enable the [feature flag](https://gitlab.com/gitlab-org/gitlab/-/issues/410191) by default for Self-Managed instances in GitLab 16.8. + stage: Secure + self-managed: true + gitlab-com: true + available_in: [Ultimate] + documentation_link: https://docs.gitlab.com/ee/user/application_security/sast/#merge-request-changes-view + image_url: https://img.youtube.com/vi/COaFZ5aNnZs/hqdefault.jpg # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/hCAyCTacdAQ/hqdefault.jpg + published_at: 2023-12-21 + release: 16.7 + +- name: CI/CD Catalog - Beta release + description: | # Do not modify this line, instead modify the lines below. + GitLab 16.7 sees the Beta release of the CI/CD catalog! The catalog is where you can search for [CI/CD components](https://docs.gitlab.com/ee/ci/components/) maintained by you, your organization, or the public community. This is the place where DevOps engineers come together to create, contribute, and share reusable pipeline configurations. + + Unlike other methods of reusing CI/CD configuration, CI/CD components published in the catalog have an improved experience, and are easily added to your pipeline. We invite you to start testing this new and exciting feature! You can try out components that others have created and shared in the catalog, or create your own components and share them with everyone. + + While this is our initial beta release of the feature, we continue to work on making the experience even better. Our goal is to make the CI/CD catalog a fundamental part of the GitLab CI/CD experience. + stage: Verify + self-managed: true + gitlab-com: true + available_in: [Free, Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/ci/components/#cicd-catalog + image_url: https://img.youtube.com/vi/NTbUq30NA7U/hqdefault.jpg + published_at: 2023-12-21 + release: 16.7 |