📝 docs(migration): refresh capability maps - #1865
Merged
Merged
Conversation
Replace stale product comparisons with mappings verified against shipped Peryx behavior and current primary sources. Distinguish management identities from artifact credentials, and require release-time review when compared capabilities change.
Merging this PR will not alter performance
Comparing 
Footnotes
|
Documentation build overview
7 files changed ·
|
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.
The PyPI migration guides described Peryx before protected reads, scoped tokens, external identity login, distributed availability, S3 storage, and retention planning. Several competitor descriptions had also fallen behind current releases, including CodeArtifact's Simple API support and pypicloud's declared Python range.
These comparisons now distinguish management identities from artifact credentials, cite current vendor or project documentation, and map each workflow to shipped Peryx behavior. The release checklist now requires another review whenever a compared capability changes.
Closes #1160