Change hl7.fhir.uv.extensions autoload to use 'latest' version (v2.x) #1247
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.
With the release of FHIR R5, the
hl7.fhir.uv.extensions
package got its first official release (1.0.0). As per this conversation, SUSHI and IG Publisher should automatically load the latest published version ofhl7.fhir.uv.extensions
. Prior to this PR, we autoloaded thecurrent
version instead.Note that I needed to enhance the logic for detecting
latest
so that it will fall back topackages2.fhir.org
if there is no manifest for the package onpackages.fhir.org
(which is the case forhl7.fhir.uv.extensions
).To test this manually, create an R5 IG. When you run the
v2.x
branch, you'll see it pull down thecurrent
version ofhl7.fhir.uv.extensions
. When you run this PR branch, you should see it pull down version1.0.0
instead.Implements CIMPL-1083.