Note deprecated SAST analyzers

What does this MR do?

Note deprecated SAST analyzers.

Related issues

17.0 Static Analysis Deprecations (#431123 - closed)

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product tier badge under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

added docsimprovement documentation maintenancerefactor typemaintenance labels

assigned to @rdickenson

added devopssecure groupstatic analysis labels

added sectionsec label

	1 Warning
	91da8b3f: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/user/application_security/sast/analyzers.md (Link to current live version)
• doc/user/application_security/sast/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

changed the description

changed milestone to %16.10

added docs-only label

added 1 commit

• 7e3eed0a - Change future planned statement

Compare with previous version

added 1 commit

• 921cc9a3 - Edits per review feedback

Compare with previous version

requested review from @amarpatel

resolved all threads

marked this merge request as ready

approved this merge request

@rdickenson I'm marking this as ready and approving it based on our Slack discussion. Appreciate the on this and your attention to detail . Let me know if there's any additional support needed here and I'll be sure to keep driving this forward as you approach the weekend.

marked the checklist item If the content requires it, ensure the information is reviewed by a subject matter expert. as completed

requested review from @eread

@eread Could you please review this MR, and merge it if you approve?

approved this merge request

Hi @eread ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. You're welcome to improve it.

added Technical Writing label

merged

resolved all threads

mentioned in commit 159d598d

mentioned in merge request !143999 (merged)

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-staging label and removed workflowproduction label

added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label

added Category:SAST label