Stream: tooling
Topic: registry.fhir.org missing update of ch-epr-term 2.0.7
Oliver Egger (Feb 10 2022 at 09:49):
@Ward Weistra we are bit lost why our latest version of ch-epr-term is not showing up (version 2.0.7) in the registry.fhir.org
- version 2.0.6 is registered here https://registry.fhir.org/package/ch.fhir.ig.ch-epr-term%7C2.0.6
- version 2.0.7 is published here http://fhir.ch/ig/ch-epr-term/index.html and here https://fhir.ch/ig/ch-epr-term/2.0.7/index.html
- we have registered it in the package-feed here https://fhir.ch/package-feed.xml and in https://fhir.ch/fhir-ig-list.json
we have an old package version of this registered in https://github.com/FHIR/ig-registry/blob/master/fhir-ig-list.json as it is described in https://confluence.hl7.org/display/FHIR/FHIR+Package+Registry+User+Documentation, and we assume that our above feed is registered in the 'It needs to be accessible by the registry feed service.' since version 2.0.6 is up.
Is there something else we need to do? Thanks if you can help us troubleshoot that.
Ward Weistra (Feb 10 2022 at 15:22):
Hi @Oliver Egger, there's an issue with the value for type, see https://chat.fhir.org/#narrow/stream/179239-tooling/topic/Publishing.20Feeds/near/271435123
Ward Weistra (Feb 10 2022 at 15:23):
Downloading package: ch.fhir.ig.ch-epr-term version: 2.0.7
Publishing to: https://packages.simplifier.net
400 BadRequest -- fhir.ig is not a valid value for type
It's a value in your package.json
Ward Weistra (Feb 10 2022 at 15:27):
See https://confluence.hl7.org/display/FHIR/NPM+Package+Specification#NPMPackageSpecification-Packagemanifest for the valid versions. In that thread I linked, I think I take away the publisher filled that with incorrect values at one point.
Oliver Egger (Feb 10 2022 at 16:16):
thanks @Ward Weistra , IGPublisher creates fhir.ig as type directly in package.json, I just verified with the lastest version, will ask in IG stream if this can overwritten somehow ...
Oliver Egger (Feb 10 2022 at 22:07):
@Ward Weistra tried to fix it, how often is this feed with the packages processed? is the log accessible directly?
Grahame Grieve (Feb 10 2022 at 22:14):
the log is not accessible. That's a todo for firely. but you shouldn't have to fix it - there's lots of packages with those values that have already been published
Oliver Egger (Feb 10 2022 at 22:24):
agree - the strange thing is, that the latest update to 2.0.6 was published in January and this was picked up in the registry. it worries me, because dependent ig's are still loading 2.0.6 (we specified it with 2.0.x) and we would like to publish the dependent ig's ... yak shaving ....
Oliver Egger (Feb 11 2022 at 07:10):
Oliver Egger said:
Ward Weistra tried to fix it, how often is this feed with the packages processed? is the log accessible directly?
it got processed now, https://registry.fhir.org/package/ch.fhir.ig.ch-epr-term%7C2.0.7 :tada:
Last updated: Apr 12 2022 at 19:14 UTC
