Fix: Add backward compatibility for legacy platform-urls config#8
Merged
Merged
Conversation
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.
This PR restores backward compatibility for packages still using the legacy
extra.platform-urlskey while keepingextra.artifactsas the preferred configuration. It routes both config styles through the same resolution flow, adds a deprecation notice for the legacy key, and includes integration coverage to ensure legacy installs continue to work correctly.Motivation and Context
After introducing the v2 artifacts model, existing packages using
platform-urlscould break during migration windows where maintainers need to support both old and new plugin versions. This PR ensures a smooth transition by accepting legacy configuration without changing current v2 behavior, so package authors can safely depend on^1.1 || ^2.0style compatibility while planning gradual config migration.Breaking Changes
None.