[docs-scanner] DCT retirement notice missing from trust documentation pages
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
- #26287 von @nielskaspers — ohne Merge geschlossen
Bewertung
- Schwierigkeit
- 1/5
- Geschätzter Aufwand
- 1-3 Stunden
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Dokumentation
- Klarheit
- Klar beschrieben
- Aktivitätsstatus
- Veraltet
- Tech-Stack
- markdown
- Bereich
- documentation
Rechercherichtung
Read the existing retirement warning in content/manuals/engine/security/trust/_index.md and compare it with the five listed trust pages. Add the specified notice, shutdown date, and retirement-documentation link to each page, then verify all five render with the warning at the top. A linked open pull request is already present, so check its status before starting.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Files:
content/manuals/engine/security/trust/deploying_notary.mdcontent/manuals/engine/security/trust/trust_automation.mdcontent/manuals/engine/security/trust/trust_delegation.mdcontent/manuals/engine/security/trust/trust_key_mng.mdcontent/manuals/engine/security/trust/trust_sandbox.md
Issue
The main index page (_index.md) contains a prominent warning that Docker Content Trust is being retired:
Docker Content Trust (DCT) is being retired. The Notary v1 service at
notary.docker.iowill shut down on December 8, 2026.
However, all five other pages in this directory provide detailed how-to instructions for using DCT with no mention of this retirement or deprecation. These pages read as if DCT is a current, fully-supported feature:
deploying_notary.md- "The easiest way to deploy Notary Server is by using Docker Compose"trust_automation.md- "It is very common for Docker Content Trust to be built into existing automation systems"trust_delegation.md- "Delegations in Docker Content Trust (DCT) allow you to control who can and cannot sign an image tag"trust_key_mng.md- "Trust for an image tag is managed through the use of keys"trust_sandbox.md- "This page explains how to set up and use a sandbox for experimenting with trust"
Why this matters
A reader who navigates directly to any of these five pages (via search, link, or navigation) will follow detailed instructions to set up and use DCT without knowing it's being retired. They may invest significant time configuring DCT only to discover later that:
- The service is shutting down in December 2026
- They need to migrate to an alternative solution
- The feature they just learned is deprecated
This is particularly problematic for the automation and delegation pages, which describe integration patterns that would require significant investment.
Suggested fix
Add a deprecation notice at the top of each of these five pages, similar to the warning in _index.md. The notice should:
- State that DCT is being retired
- Mention the December 8, 2026 shutdown date
- Link to the retirement documentation at
/manuals/retired.md#docker-content-trust-dct
Example:
> [!WARNING]
>
> Docker Content Trust (DCT) is being retired. The Notary v1 service at
> `notary.docker.io` will shut down on December 8, 2026. For more information, see
> [Docker Content Trust (DCT)](/manuals/retired.md#docker-content-trust-dct).
Found by nightly documentation quality scanner
- Vorherrschende Sprache
- Markdown
- Sterne
- 4.7k
- Forks
- 8.5k
- Ø Merge
- 2 T. 11 Std.
- Gemergte PRs (30 T.)
- 135
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus docker/docs
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 95/100
Maintainer antworten meist innerhalb von 1 Tag
-
[docs-scanner] S3 and Azure Blob cache backends marked as unreleased but have complete documentationOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag
-
status/triage
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 92/100
Maintainer antworten meist innerhalb von 1 Tag
-
[docs-scanner] Confusing explanation of approval-required outcome vs permit in MCP policyEvtl. vergeben @dave123981 hat das vor 3 Tagen übernommen. Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
Maintainer antworten meist innerhalb von 1 Tag
Ähnliche Issues
-
Contribute FeedbackOffen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 67/100
MicrosoftDocs/WSL#2654 ·
-
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 85/100
hibernate/hibernate-reactive#4485 ·
Maintainer antworten meist innerhalb von 1 Tag
-
vuln:LOW
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 63/100
curl/curl-www#679 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
mxschmitt/awesome-playwright#285 ·
Maintainer antworten meist innerhalb von 19 Tagen
-
area/access-management Frontend onboarding candidate :handshake:
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
Altinn/altinn-auth#4941 ·
Maintainer antworten meist innerhalb von 1 Tag