Improve SolutionLibraries Transitive Dependency handling#137
Merged
MichielOda merged 3 commits intoSkylineCommunications:mainfrom Mar 4, 2026
Merged
Conversation
Refactored package name extraction for SolutionLibraries in AutomationScriptBuilder. Updated NuGetHelper to process SolutionLibrary dependencies. Added new test projects and cases to verify correct handling of SolutionLibrary NuGet packages and their dependencies, including custom and nested scenarios.
MichielOda
approved these changes
Mar 4, 2026
This was referenced Mar 4, 2026
Merged
This was referenced Mar 6, 2026
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
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.
Pull Request Description
This PR ensures that dependencies of DevPacks (SolutionLibraries) are correctly resolved in automation scripts and handled appropriately during script packaging. In automation scripts, all dependencies of DevPacks are resolved and included, even if some dependencies are other DevPacks. During packaging, DevPack assemblies themselves are not included, as they are expected to already be present on the target system. Previously, DevPack dependencies were not reliably resolved, which could lead to missing assemblies in the final package.
Key Changes
Impact