Cancel previously-announced change to MobSF
What does this MR do?
Update the previously-announced MobSF change notice to state that the change is no longer happening.
Per @jamesliu-gitlab in gitlab-org/security-products/analyzers/mobsf!73 (comment 1387767716):
The deprecation warnings no longer apply due to this change -- we now support proper scanning of multimodule Android projects and more.
Choice: delete the notice entirely, or update the contents?
I chose to update the contents in case the breaking change notice had been linked to elsewhere. Someone might have a link to https://docs.gitlab.com/ee/update/deprecations.html#changing-mobsf-based-sast-analyzer-behavior-in-multi-module-android-projects. If they did and we totally removed it, they'd just land at the top of the Deprecations page with no information about the deprecation being cancelled.
Related issues
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
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 likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure 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.