Fast, portable and reliable dependency analysis for any codebase. Supports license & vulnerability scanning for large monoliths. Language-agnostic; integrates with 20+ build systems.
Before the changes, the license file match contents appeared as:
After some investigation, it was discovered that the revision's license scan type was being set to full_files . This shouldn't have been the case because the given repro case should've had the scan type set to match_data
Note: Refer to the linked ANE ticket for repro case
Acceptance criteria
Ensure that the contents of the license file matches are not empty
Testing plan
fossa analyze on the project linked in the ANE ticket
Check the license file match contents
Check that the license scan type is set to the proper type: match_data
[x] I added tests for this PR's change (or explained in the PR description why tests don't make sense).
[x] If this PR introduced a user-visible change, I added documentation into docs/.
[x] If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
[x] 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.
[x] If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. 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).
[x] If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.
Overview
The changes from pr: Support true forced rebuilds for vendored dependencies, refactor types introduced a bug that caused the contents of the license file matches to be empty.
Before the changes, the license file match contents appeared as:
After some investigation, it was discovered that the revision's license scan type was being set to
full_files. This shouldn't have been the case because the given repro case should've had the scan type set tomatch_dataNote: Refer to the linked ANE ticket for repro case
Acceptance criteria
Testing plan
fossa analyzeon the project linked in the ANE ticketmatch_dataRisks
Metrics
References
Checklist
docs/.docs/README.msand gave consideration to how discoverable or not my documentation is.Changelog.md. If this PR did not mark a release, I added my changes into an# Unreleasedsection at the top..fossa.ymlorfossa-deps.{json.yml}, I updateddocs/references/files/*.schema.jsonAND I have updated example files used byfossa initcommand. 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).docs/references/subcommands/<subcommand>.md.