Remove premature 19.4 release note "Vulnerability report filters are used for CSV export"

What does this MR do and why?

Removes the release note item Vulnerability report filters are used for CSV export from the GitLab 19.4 release notes. It went in through !253271 (merged).

It's currently published at https://docs.gitlab.com/releases/19/gitlab-19-4-released/#vulnerability-report-filters-are-used-for-csv-export.

The feature hasn't shipped on any offering yet:

  • vulnerability_csv_export_filters is still default_enabled: false in ee/config/feature_flags/gitlab_com_derisk/. So self-managed and Dedicated have it off entirely, which makes the note's offering line wrong for both.
  • On GitLab.com the flag is only enabled for the gitlab-org/gitlab project. The rollout in #581520 (closed) paused on Sep 3 after a statement timeout on large projects. The fix for that timeout (!253454 (merged)) merged on Sep 24 in 19.5, and the rollout hasn't picked back up yet.
  • The feature issue #579107 is still open.

This is the same thing that happened in 19.2, where !249744 (merged) pulled the note for the same reason.

Customers are already asking about it, which is how this got flagged.

When the item is re-added for the milestone where the rollout actually finishes, it should say the filters apply to project-level exports only. Group-level and instance-level exports still ignore filters on purpose (#627590).

Changes

One file deleted: doc/releases/19/gitlab-19-4-released/honor-filters-for-vulnerability-exports.md.

  • No backport needed. The file isn't on 19-4-stable-ee, because !253271 (merged) merged after 19.4 was cut, and the docs site builds from master.
  • No ja-jp counterpart exists for this item, so there's nothing for localization to clean up.

MR acceptance checklist

  • Documentation-only change; no code, tests, or migrations.
  • Technical Writing review.

/cc @ajbiton

Merge request reports

Loading
Loading