Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add support for SwiftPM v2 lockfiles #957

Merged
merged 2 commits into from
Jun 3, 2022

Conversation

elldritch
Copy link
Member

Overview

This PR implements PS-26, adding support for SwiftPM v2 Package.resolved files.

Acceptance criteria

SwiftPM projects using version 2 of Package.resolved now analyze correctly.

Testing plan

Find a SwiftPM project using v2 of Package.resolved and analyze it. Some example projects:

References

Checklist

  • I added tests for this PR's change (or explained in the PR description why tests don't make sense).
  • If this PR introduced a user-visible change, I added documentation into docs/.
  • If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an # Unreleased section at the top.
  • If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).

@elldritch elldritch requested a review from a team as a code owner June 3, 2022 19:45
@elldritch elldritch requested a review from zlav June 3, 2022 19:45
Copy link
Contributor

@meghfossa meghfossa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@elldritch elldritch merged commit 929f3eb into master Jun 3, 2022
@elldritch elldritch deleted the PS-26-swiftpm-resolved-v2-parsing branch June 3, 2022 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants