When a dependency uses the "latest" version in sushi-config.yaml, SUSHI must populate the generated IG JSON with the real version number (not "latest"). PR #1409 fixes this for dependency packages that contain an ImplementationGuide resource, but it does not address the case were a dependency package does not have an ImplementationGuide resource. In this case, we should fall back to the package's package.json file.
When a dependency uses the "latest" version in sushi-config.yaml, SUSHI must populate the generated IG JSON with the real version number (not "latest"). PR #1409 fixes this for dependency packages that contain an ImplementationGuide resource, but it does not address the case were a dependency package does not have an ImplementationGuide resource. In this case, we should fall back to the package's package.json file.
This was raised on Zulip here: https://chat.fhir.org/#narrow/stream/215610-shorthand/topic/automatically.20get.20latest.20dependencies/near/419233182