Explicitly state support for TypeScript

What does this MR do and why?

Describe in detail what your merge request does and why.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

changed milestone to %15.6

added groupcomposition analysis typemaintenance labels

requested review from @adamcohen

assigned to @sam.white

added devopssecure sectionsec labels

@adamcohen could you take a look at this? Would it be accurate to add both Kotlin and Typescript to this table? The fact that we don't mention them in the table causes confusion about what we support.

added documentation label

	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/dependency_scanning/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

👋 @sam.white - please see the following guidance and update this merge request.

	1 Warning
⚠	Please add a subtype label to this merge request.

If you have added a type label and do not feel the purpose of this merge request matches one of the subtypes labels, please resolve this discussion.

@sam.white I don't think we should go into this level of detail in our documentation, for the reasons discussed here. Let me know if you disagree.

changed title from Explicitly state support for Kotlin and Typescript to Explicitly state support for Kotlin and TypeScript

added 1 commit

• 59ea9da4 - Apply 2 suggestion(s) to 1 file(s)

Compare with previous version

changed title from Explicitly state support for Kotlin and TypeScript to Explicitly state support for TypeScript

added maintenanceusability label

resolved all threads

approved this merge request

requested review from @rdickenson

@rdickenson could you please review and merge?

added Technical Writing docsimprovement labels

approved this merge request

merged

@rdickenson, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline finished more than 2 hours ago, you should:

1. Ensure the merge request is not in Draft status.
2. Start a pipeline (especially important for Community contribution merge requests).
3. Set the merge request to merge when pipeline succeeds.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

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

resolved all threads

mentioned in commit 21a32471

resolved all threads

resolved all threads

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

mentioned in issue #337083 (closed)