diff --git a/doc/architecture/blueprints/cells/infrastructure/deployments.md b/doc/architecture/blueprints/cells/infrastructure/deployments.md
index 9df84bcc368c3786be6530ef6a30a3788e519074..9776ff4af707d812150039967b4ef895f8007fb6 100644
--- a/doc/architecture/blueprints/cells/infrastructure/deployments.md
+++ b/doc/architecture/blueprints/cells/infrastructure/deployments.md
@@ -8,7 +8,7 @@ coach:
approvers: []
---
-Disclaimer: This blueprint requires more cross-functional alignment - [Confidence Level] --> Low
+Disclaimer: This blueprint requires more cross-functional alignment - **Confidence Level:** Low
# Application Deployment with a Cellular Architecture
diff --git a/doc/architecture/blueprints/gitlab_ml_experiments/index.md b/doc/architecture/blueprints/gitlab_ml_experiments/index.md
index 2aa23997cebfd3eb8f1f2e31430e74a30384fe02..888d112bfafbe6850c12f5059192327278b21793 100644
--- a/doc/architecture/blueprints/gitlab_ml_experiments/index.md
+++ b/doc/architecture/blueprints/gitlab_ml_experiments/index.md
@@ -123,7 +123,7 @@ However, Service-Integration will establish certain necessary and optional requi
| ID | Required | Detail | Epic/Issue | Done? |
|---|---|---|---|---|
| `R100` | Required | The platform should be easy to use: imagine Heroku with [GitLab Production Readiness-approved](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/readiness/) defaults. | [Runway to [BETA] : Increased Adoption and Self Service](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1115) | **{dotted-circle}** No |
-| `R110` | Required | With the exception of an Infrastructure-led onboarding process, services are owned, deployed and managed by stage-group teams. In other words,services follow a “You Build It, You Run It†model of ownership.| [[Paused] Discussion: Tiered Support Model for Runway](https://gitlab.com/gitlab-com/gl-infra/platform/runway/team/-/issues/97) | **{dotted-circle}** No |
+| `R110` | Required | With the exception of an Infrastructure-led onboarding process, services are owned, deployed and managed by stage-group teams. In other words,services follow a "You Build It, You Run It" model of ownership.| [[Paused] Discussion: Tiered Support Model for Runway](https://gitlab.com/gitlab-com/gl-infra/platform/runway/team/-/issues/97) | **{dotted-circle}** No |
| `R120` | Required | Programming-language agnostic: no requirements for services. Services should be packaged as container images.| [Runway to [BETA] : Increased Adoption and Self Service](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/1115) | **{dotted-circle}** No |
| `R130` | Recommended | Each service should be evaluated against the GitLab.com [Service Maturity Model](https://handbook.gitlab.com/handbook/engineering/infrastructure/service-maturity-model/).| [Discussion: Introduce an 'Infrastructure Well-Architected Service Framework'](https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2537) | **{dotted-circle}** No |
| `R140` | Recommended | Services using the platform have expedited production-readiness processes. {::nomarkdown}<ol><li>Production-readiness requirements graded by service maturity: low-traffic, low-maturity experimental services will have lower requirement thresholds than more mature services. </li><li> By default, the platform should provide services with defaults that would pass production-readiness review for the lowest service maturity-level. </li><li> At introduction, lowest maturity services can be deployed without production readiness, provided the meet certain automatically validated requirements. This removes Infrastructure gate-keeping from being a blocker to experimental service delivery.</li></ol>{:/} | | |
diff --git a/doc/development/fe_guide/frontend_goals.md b/doc/development/fe_guide/frontend_goals.md
index c9569d9a41e3e15da657932a8eb80f75adffebf1..a19836cfeee163c27d365618ff2d4b1dbdfa9ea6 100644
--- a/doc/development/fe_guide/frontend_goals.md
+++ b/doc/development/fe_guide/frontend_goals.md
@@ -17,7 +17,7 @@ Keeping up with the latest version of Vue ensures that the GitLab frontend lever
**Current Status**
- **As of December 2023**: GitLab is currently using Vue 2.x.
-- **Progress**: [Brief description of progress]
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -26,11 +26,11 @@ Keeping up with the latest version of Vue ensures that the GitLab frontend lever
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
@@ -38,12 +38,12 @@ Keeping up with the latest version of Vue ensures that the GitLab frontend lever
### State Management
-When global state management is needed, it should happen in Apollo instead of Vuex or other state management libraries. See [https://docs.gitlab.com/ee/development/fe_guide/migrating_from_vuex.html](migrating_from_vuex.md) for more details regarding why and how we plan on migrating.
+When global state management is needed, it should happen in Apollo instead of Vuex or other state management libraries. See [Migrating from Vuex](migrating_from_vuex.md) for more details regarding why and how we plan on migrating.
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -52,24 +52,24 @@ When global state management is needed, it should happen in Apollo instead of Vu
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
### HAML by default
-We'll continue using HAML over Vue when appropriate. See [https://docs.gitlab.com/ee/development/fe_guide/vue.html#when-to-add-vue-application](vue.md#when-to-add-vue-application) on how to decide when Vue should be chosen.
+We'll continue using HAML over Vue when appropriate. See [when to add Vue application](vue.md#when-to-add-vue-application) on how to decide when Vue should be chosen.
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -78,15 +78,15 @@ We'll continue using HAML over Vue when appropriate. See [https://docs.gitlab.co
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
### Complete removal of jQuery
@@ -94,8 +94,8 @@ In 2019 we committed to no longer use jQuery, however we have not prioritized fu
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -104,15 +104,15 @@ In 2019 we committed to no longer use jQuery, however we have not prioritized fu
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
### Dependencies management
@@ -120,8 +120,8 @@ Similar to keeping on the latest major version of Vue, we should try to keep as
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -130,15 +130,15 @@ Similar to keeping on the latest major version of Vue, we should try to keep as
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
## Best Practices
@@ -168,8 +168,8 @@ For navigation between clusters, we can still rely on Rails routing. These cases
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -178,15 +178,15 @@ For navigation between clusters, we can still rely on Rails routing. These cases
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
### Reusable components
@@ -203,8 +203,8 @@ This is currently under development. Follow the [GitLab Modular Monolith for FE]
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -213,15 +213,15 @@ This is currently under development. Follow the [GitLab Modular Monolith for FE]
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
### Migrate to PostCSS
@@ -229,8 +229,8 @@ SASS compilation takes almost half of the total frontend compilation time. This
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -239,15 +239,15 @@ SASS compilation takes almost half of the total frontend compilation time. This
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
## Collaboration and Tooling
@@ -257,8 +257,8 @@ We're early in the process of adding visual testing, but we should have a framew
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -267,15 +267,15 @@ We're early in the process of adding visual testing, but we should have a framew
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
### Accessibility testing
@@ -283,8 +283,8 @@ In 2023 we determined the tooling for accessibility testing. We opted for axe-co
**Current Status**
-- **As of December 2023**: [Status]
-- **Progress**: [Brief description of progress]
+- **As of December 2023**: (Status)
+- **Progress**: (Brief description of progress)
**Responsible Team**
@@ -293,12 +293,12 @@ In 2023 we determined the tooling for accessibility testing. We opted for axe-co
**Milestones and Timelines**
-- [Key milestones, expected completions]
+- (Key milestones, expected completions)
**Challenges and Dependencies**
-- [Any major challenges]
+- (Any major challenges)
**Success Metrics**
-- [Potential metrics]
+- (Potential metrics)
diff --git a/doc/solutions/cloud/aws/gitlab_aws_integration.md b/doc/solutions/cloud/aws/gitlab_aws_integration.md
index 904f290733907cb6647386359e5648b19a5250d8..58ef93d24f6e84d26ce45cb4ac28154ac6980398 100644
--- a/doc/solutions/cloud/aws/gitlab_aws_integration.md
+++ b/doc/solutions/cloud/aws/gitlab_aws_integration.md
@@ -54,7 +54,7 @@ Documentation and References:
#### AWS CodePipeline Integrations
-[AWS CodePipeline Integration](https://docs.aws.amazon.com/codepipeline/latest/userguide/connections-gitlab.html) - by using GitLab as CodeStar Connections source for CodePipeline, additional AWS service integrations are available. [[12/28/2023](https://aws.amazon.com/about-aws/whats-new/2023/12/codepipeline-gitlab-self-managed/)] `[AWS Built]`
+[AWS CodePipeline Integration](https://docs.aws.amazon.com/codepipeline/latest/userguide/connections-gitlab.html) - by using GitLab as CodeStar Connections source for CodePipeline, additional AWS service integrations are available. ([12/28/2023](https://aws.amazon.com/about-aws/whats-new/2023/12/codepipeline-gitlab-self-managed/)) `[AWS Built]`
AWS Services that are supported by an AWS CodePipeline integration:
diff --git a/doc/user/application_security/sast/analyzers.md b/doc/user/application_security/sast/analyzers.md
index 18eaa0582eccf546e35a73a74796d7b1bbb6d87e..cac00b069e008637d05cf96fbea90e30dae8562e 100644
--- a/doc/user/application_security/sast/analyzers.md
+++ b/doc/user/application_security/sast/analyzers.md
@@ -44,7 +44,7 @@ SAST supports the following official analyzers:
<html>
<small>Footnotes:
<ol>
- <li>These analyzers were [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/431123) in GitLab 16.9</a> and are planned for removal in 17.0. The <a href="https://gitlab.com/gitlab-org/security-products/analyzers/semgrep">Semgrep analyzer</a> is proposed as their replacement.</li>
+ <li>These analyzers were <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/431123">deprecated</a> in GitLab 16.9 and are planned for removal in 17.0. The <a href="https://gitlab.com/gitlab-org/security-products/analyzers/semgrep">Semgrep analyzer</a> is proposed as their replacement.</li>
</ol>
</small>
</html>
diff --git a/doc/user/application_security/sast/index.md b/doc/user/application_security/sast/index.md
index 4b20269ccf7d5c0efb63ed331ade98de3bdd9d95..83fe443f833ab11c7fe87d0d0dcc1b8cfadb2662 100644
--- a/doc/user/application_security/sast/index.md
+++ b/doc/user/application_security/sast/index.md
@@ -86,9 +86,7 @@ For more information about our plans for language support in SAST, see the [cate
<li>The SpotBugs-based analyzer supports <a href="https://gradle.org/">Gradle</a>, <a href="https://maven.apache.org/">Maven</a>, and <a href="https://www.scala-sbt.org/">SBT</a>. It can also be used with variants like the <a href="https://docs.gradle.org/current/userguide/gradle_wrapper.html">Gradle wrapper</a>, <a href="https://grails.org/">Grails</a>, and the <a href="https://github.com/takari/maven-wrapper">Maven wrapper</a>. However, SpotBugs has <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/350801">limitations</a> when used against <a href="https://ant.apache.org/">Ant</a>-based projects. You should use the Semgrep-based analyzer for Ant-based Java or Scala projects.</li>
</ol>
<ol>
- <li>
- These analyzers were <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/431123">deprecated in GitLab 16.9</a> and are planned for removal in 17.0. The <a href="https://gitlab.com/gitlab-org/security-products/analyzers/semgrep">Semgrep analyzer</a> is proposed as their replacement.</li>
- </li>
+ <li> These analyzers were <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/431123">deprecated in GitLab 16.9</a> and are planned for removal in 17.0. The <a href="https://gitlab.com/gitlab-org/security-products/analyzers/semgrep">Semgrep analyzer</a> is proposed as their replacement.</li>
</ol>
</html>
@@ -98,8 +96,8 @@ GitLab has reached [End of Support](https://about.gitlab.com/handbook/product/gi
| Language / framework | [Analyzer](analyzers.md) used for scanning | Minimum supported GitLab version | End Of Support GitLab version |
|------------------------------|--------------------------------------------------------------------------------------------------------------| --------------------------------- | ------------------------------------------------------------- |
-| .NET Core | [Security Code Scan](https://gitlab.com/gitlab-org/security-products/analyzers/security-code-scan) | 11.0 | [16.0](https://gitlab.com/gitlab-org/gitlab/-/issues/390416) |
-| .NET Framework | [Security Code Scan](https://gitlab.com/gitlab-org/security-products/analyzers/security-code-scan) | 13.0 | [16.0](https://gitlab.com/gitlab-org/gitlab/-/issues/390416) |
+| .NET Core | [Security Code Scan](https://gitlab.com/gitlab-org/security-products/analyzers/security-code-scan) | 11.0 | [16.0](https://gitlab.com/gitlab-org/gitlab/-/issues/390416) |
+| .NET Framework | [Security Code Scan](https://gitlab.com/gitlab-org/security-products/analyzers/security-code-scan) | 13.0 | [16.0](https://gitlab.com/gitlab-org/gitlab/-/issues/390416) |
| Go | [Gosec](https://gitlab.com/gitlab-org/security-products/analyzers/gosec) | 10.7 | [15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/352554) |
| Java | [SpotBugs](https://gitlab.com/gitlab-org/security-products/analyzers/spotbugs) with the find-sec-bugs plugin | 10.6 (Maven), 10.8 (Gradle) & 11.9 (SBT) | [15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/352554) |
| Python | [bandit](https://gitlab.com/gitlab-org/security-products/analyzers/bandit) | 10.3 | [15.4](https://gitlab.com/gitlab-org/gitlab/-/issues/352554) |