scout: retire features

_vale/config/vocabularies/Docker/accept.txt

@@ -225,6 +225,7 @@ Sigstore
 Snyk
 Solr
 SonarQube
+Sonatype
 Sonoma
 Splunk
 SQLite

content/guides/docker-scout.md

@@ -247,22 +247,22 @@ control over your image's security.
 
 {{< youtube-embed jM9zLBf8M-8 >}}
 
-Docker Scout's [remediation feature](/manuals/scout/policy/dashboard.md)
-helps you address supply chain and security issues by offering tailored
-recommendations based on policy evaluations. These recommendations guide you in
-improving policy compliance or enhancing image metadata, allowing Docker Scout
-to perform more accurate evaluations in the future.
+Docker Scout's remediation feature helps you address supply chain and
+security issues by offering tailored recommendations based on policy
+evaluations. These recommendations guide you in improving policy compliance
+or enhancing image metadata, allowing Docker Scout to perform more accurate
+evaluations in the future.
 
 You can use this feature to ensure that your base images are up-to-date and
 that your supply chain attestations are complete. When a violation occurs,
 Docker Scout provides recommended fixes, such as updating your base image or
 adding missing attestations. If there isn’t enough information to determine
 compliance, Docker Scout suggests actions to help resolve the issue.
 
-In the Docker Scout Dashboard, you can view and act on these recommendations by
-reviewing violations or compliance uncertainties. With integrations like
-GitHub, you can even automate updates, directly fixing issues from the
-dashboard.
+You can view and act on these recommendations in Docker Desktop or Docker Hub,
+see [Remediation recommendations](/manuals/scout/explore/image-details-view.md#remediation-recommendations),
+or from the CLI with
+[`docker scout recommendations`](/reference/cli/docker/scout/recommendations/).
 
 <div id="scout-lp-survey-anchor"></div>
 

content/manuals/build/building/best-practices.md

@@ -259,15 +259,15 @@ checks if pinned digests in your Dockerfile correspond to the correct version.
 If a publisher updates an image that you've pinned, the policy evaluation
 returns a non-compliant status, indicating that you should update your image.
 
-Docker Scout also supports an automated remediation workflow for keeping your
-base images up-to-date. When a new image digest is available, Docker Scout can
-automatically raise a pull request on your repository to update your
-Dockerfiles to use the latest version. This is better than using a tag that
-changes the version automatically, because you're in control and you have an
-audit trail of when and how the change occurred.
-
-For more information about automatically updating your base images with Docker
-Scout, see [Remediation](/manuals/scout/policy/dashboard.md).
+To keep your base images up-to-date automatically, use
+[GitHub Dependabot](https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)
+with `package-ecosystem: "docker"`. Dependabot raises pull requests to update
+your base image tags and digests on a schedule. This is better than using a tag
+that changes the version automatically, because you're in control and you have
+an audit trail of when and how the change occurred.
+
+You can also review available base image updates from the CLI with
+[`docker scout recommendations`](/reference/cli/docker/scout/recommendations/).
 
 ## Build and test your images in CI
 

content/manuals/retired.md

@@ -65,6 +65,9 @@ aliases:
   - /desktop/features/dev-environments/
   - /scout/policy/scores/
   - /scout/integrations/environment/sysdig/
+  - /scout/integrations/team-collaboration/slack/
+  - /scout/integrations/code-quality/sonarqube/
+  - /scout/integrations/source-code-management/github/
 ---
 
 This document provides an overview of Docker features, products, and
@@ -160,23 +163,31 @@ details, see the [Scout platform release notes](/manuals/scout/release-notes/pla
   Retired July 1, 2026.
 - GitHub source code management integration: linked images to their source
   repository and automated base-image updates via PRs. Retired July 1, 2026.
-  For migration options, see
-  [GitHub integration](/manuals/scout/integrations/source-code-management/github.md).
-- Notifications: alerted users to newly disclosed CVEs in-product and by email.
-  Deprecated, retiring September 1, 2026.
+  For base-image updates, use
+  [GitHub Dependabot](https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)
+  with `package-ecosystem: "docker"`. For image-to-source linkage, build with
+  `--provenance=mode=max`. This retirement doesn't affect the
+  [`docker/scout-action`](https://github.com/docker/scout-action) GitHub Action
+  for CI pipelines.
 - Slack integration: sent vulnerability and policy compliance notifications to
-  Slack channels. Deprecated, retiring July 30, 2026. For more information,
-  see [Slack integration](/manuals/scout/integrations/team-collaboration/slack.md).
-- Amazon ECR integration: automatically analyzed images pushed to ECR
-  registries. Deprecated, retiring September 1, 2026. For migration options, see
-  [ECR integration](/manuals/scout/integrations/registry/ecr.md).
-- Azure Container Registry integration: automatically analyzed images pushed to
-  ACR registries. Deprecated, retiring September 1, 2026. For migration options,
-  see [ACR integration](/manuals/scout/integrations/registry/acr.md).
+  Slack channels. Retired July 30, 2026.
+- Notifications: alerted users to newly disclosed CVEs in-product and by
+  email. Retired September 1, 2026. To surface CVE and policy results without
+  push notifications, integrate `docker scout cves` or `docker scout policy`
+  into your CI pipeline.
+- Native Amazon ECR integration: automatically analyzed images pushed to ECR
+  registries using a CloudFormation stack. Retired September 1, 2026. Docker
+  Scout still supports ECR through
+  [`docker scout watch`](/manuals/scout/integrations/registry/_index.md).
+- Native Azure Container Registry integration: automatically analyzed images
+  pushed to ACR registries using an ARM template. Retired September 1, 2026.
+  Docker Scout still supports ACR through
+  [`docker scout watch`](/manuals/scout/integrations/registry/_index.md).
 - Policies page in the Dashboard: the `docker scout policy`
-  CLI continues to work. Deprecated, retiring September 1, 2026. See
+  CLI continues to work. Retired September 1, 2026. See
   [Evaluate policies](/manuals/scout/policy/local.md).
-- SonarQube integration: surfaced SonarQube quality gate results as a Docker Scout policy. Deprecated, retiring September 1, 2026.
+- SonarQube integration: surfaced SonarQube quality gate results as a Docker
+  Scout policy. Retired September 1, 2026.
 
 ### GitHub Copilot extension
 

content/manuals/scout/explore/dashboard.md

@@ -84,46 +84,11 @@ affected by the CVE.
 The settings menu in the Docker Scout Dashboard contains:
 
 - [**Repository settings**](#repository-settings) for enabling and disabling repositories.
-- [**Notifications**](#notification-settings) for managing your notification preferences.
 
 ### Repository settings
 
 When you enable Docker Scout for a repository,
 Docker Scout analyzes new tags automatically when you push to that repository.
-To enable repositories in Amazon ECR, Azure ACR, or other third-party registries,
-you first need to integrate them.
-See [Container registry integrations](/manuals/scout/integrations/_index.md#container-registries)
-
-### Notification settings
-
-> [!IMPORTANT]
->
-> Docker Scout notifications are deprecated and will be retired on
-> July 30, 2026. To surface CVE and policy results without push notifications,
-> integrate `docker scout cves` or `docker scout policy` into your CI pipeline.
-> See [CI integrations](/manuals/scout/integrations/_index.md#continuous-integration).
-> For details, see the
-> [Scout platform release notes](/manuals/scout/release-notes/platform.md).
-
-The [Notification settings](https://scout.docker.com/settings/notifications)
-page is where you can change the preferences for receiving notifications from
-Docker Scout. Notification settings are personal, and changing notification
-settings only affects your personal account, not the entire organization.
-
-Docker Scout notifies you when a new vulnerability is disclosed in a security
-advisory and it affects one or more of your images. Notifications are only
-triggered for the _last pushed_ image tags for each repository.
-
-The available notification settings are:
-
-- **Repository scope**: select whether you want notifications for all
-  repositories or only specific ones.
-- **Delivery preferences**: choose between in-product notification pop-ups
-  and OS-level browser notifications.
-
-You can also configure your notification settings in Docker Desktop by going
-to **Settings** > **Notifications**.
-
-From this page, you can also go to the settings for
-[Team collaboration integrations](/manuals/scout/integrations/team-collaboration/slack.md).
+To enable repositories in third-party registries, you first need to integrate
+them. See [Container registry integrations](/manuals/scout/integrations/_index.md#container-registries)
 

content/manuals/scout/integrations/_index.md

@@ -23,11 +23,9 @@ registries enables Docker Scout to run image analysis on those repositories,
 so that you can get insights into the composition of those images even if they
 aren't hosted on Docker Hub.
 
-The following container registry integrations are available:
-
-- [Amazon Elastic Container Registry](./registry/ecr.md) (deprecated, retiring September 1, 2026)
-- [Azure Container Registry](./registry/acr.md) (deprecated, retiring September 1, 2026)
-- [JFrog Artifactory](./registry/artifactory.md)
+Docker Scout integrates with any Docker/OCI-compliant registry using
+[`docker scout watch`](./registry/_index.md), including Amazon ECR, Azure
+Container Registry, JFrog Artifactory, Harbor, and Sonatype Nexus.
 
 ### Continuous Integration
 
@@ -58,39 +56,3 @@ The following environment monitoring integrations are available:
 
 For more information about environment integrations, see
 [Environments](./environment/_index.md).
-
-### Code quality
-
-Integrating Docker Scout with code analysis tools enables quality checks
-directly on source code, helping you keep track of bugs, security issues, test
-coverage, and more. In addition to image analysis and environment monitoring,
-code quality gates let you shift left your supply chain management with Docker
-Scout.
-
-Once you enable a code quality integration, Docker Scout includes the code
-quality assessments as policy evaluation results for the repositories where
-you've enabled the integration.
-
-The following code quality integrations are available:
-
-- [SonarQube](./code-quality/sonarqube.md) (deprecated, retiring September 1, 2026)
-
-### Source code management
-
-Integrate Docker Scout with your version control system to get guided
-remediation advice on how to address issues detected by Docker Scout image
-analysis, directly in your repositories.
-
-The following source code management integrations are available:
-
-- [GitHub](source-code-management/github.md) (retired)
-
-### Team collaboration
-
-Integrations in this category let you integrate Docker Scout with collaboration
-platforms for broadcasting notifications about your software supply chain in
-real-time to team communication platforms.
-
-The following team collaboration integrations are available:
-
-- [Slack](./team-collaboration/slack.md) (deprecated, retiring September 1, 2026)