The test-typescript-us-core-example CI job produces different generated files than local execution. The root cause is non-deterministic canonical URL resolution when multiple StructureDefinitions share the same short name (e.g., assertedDate resolves to condition-assertedDate locally but allergyintolerance-assertedDate on CI).
This affects ~30 generated profile files in examples/typescript-us-core/. The git diff validation step is currently commented out as a workaround (generation, typecheck, and tests still run).
Example diff from CI:
-// CanonicalURL: http://hl7.org/fhir/StructureDefinition/condition-assertedDate
+// CanonicalURL: http://hl7.org/fhir/StructureDefinition/allergyintolerance-assertedDate
Likely cause: iteration order over FHIR package contents differs between cached and freshly downloaded packages. The profile file naming uses the SD's short name which can collide across packages — the first-seen SD wins, but "first" depends on package load order.
The
test-typescript-us-core-exampleCI job produces different generated files than local execution. The root cause is non-deterministic canonical URL resolution when multiple StructureDefinitions share the same short name (e.g.,assertedDateresolves tocondition-assertedDatelocally butallergyintolerance-assertedDateon CI).This affects ~30 generated profile files in
examples/typescript-us-core/. The git diff validation step is currently commented out as a workaround (generation, typecheck, and tests still run).Example diff from CI:
Likely cause: iteration order over FHIR package contents differs between cached and freshly downloaded packages. The profile file naming uses the SD's short name which can collide across packages — the first-seen SD wins, but "first" depends on package load order.