feat: expand lockfile resolver coverage across additional ecosystems#47
Closed
DevonL wants to merge 1 commit intosplit/dependency-health-v2-01-lockfile-corefrom
Closed
Conversation
Collaborator
Author
|
Closing this PR because the initial split/stacking strategy was incorrect and produced oversized, overlapping diffs. A clean stacked PR set will be reopened from the original feature branch. |
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.
📄 Summary
PR 2 of 6 — Dependency Health V2
Adds lockfile parsers for Cargo, Composer, Dart, Docker, Go, Gradle, Helm, Hex, NuGet, Ruby, and Swift. Includes the lockfile resolver registry and test fixtures.
Base: PR #41 (lockfile core)
🔍 Related Issues
Link to any related GitHub issues (e.g.,
Fixes #12,Closes #34):🧪 Type of Change
Please check the relevant type tag for this PR title:
[FIX]Bug fix[NEW]New thing[REFACTOR]Internal changes such as code restructuring or optimization that does not alter functionality[DOC]Documentation-only changes[CHORE]Maintenance, cleanup, or CI configuration🧪 How Has This Been Tested?
Describe how you tested your changes. Include CI runs, local tests, manual verification, or screenshots if applicable.
The entirety of the Dependency Health updates were tested with a combination of automated testing, and manual testing against each of the upstream ecosystems.
📸 Screenshots (if applicable)
If UI or logs are affected, include before/after screenshots or output.
✅ Checklist