docs: remove duplicate DCT deprecation notice in content trust overview#25156
Open
Nikhilkumar2311 wants to merge 1 commit into
Open
docs: remove duplicate DCT deprecation notice in content trust overview#25156Nikhilkumar2311 wants to merge 1 commit into
Nikhilkumar2311 wants to merge 1 commit into
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
area/engine
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #25144
What changed
Removed the duplicate DCT deprecation notice from the "Signing images
with Docker Content Trust" section (lines ~127-136).
Why
The same deprecation notice already appears in the "About Docker Content
Trust (DCT)" section above. Having it twice was redundant and potentially
confusing for readers — they might think it represents two separate
deprecations or that it's an editing error.