On the last two API prod builds run after a dispatch from the bcd repo, our npm update has run before bcd's npm publish has fully propagated, and we've fetched the last but one version:
e.g. https://github.com/mdn/browser-compat-data/releases/tag/v8.0.10 was released, and kicked off a build, but 8.0.9 was fetched instead: https://github.com/mdn/bcd-utils/actions/runs/31111332021/job/92649598856#step:5:13
This is a recurrence of #133
It seems like things have gotten slower in npm land lately, so even if the npm publish command has exited, that version isn't available for everyone through npm yet.
One solution for this could be to add the version to the client_payload of the repository_dispatch and poll in the deploy job until that version appears on npm.
On the last two API prod builds run after a dispatch from the bcd repo, our
npm updatehas run before bcd'snpm publishhas fully propagated, and we've fetched the last but one version:e.g. https://github.com/mdn/browser-compat-data/releases/tag/v8.0.10 was released, and kicked off a build, but 8.0.9 was fetched instead: https://github.com/mdn/bcd-utils/actions/runs/31111332021/job/92649598856#step:5:13
This is a recurrence of #133
It seems like things have gotten slower in npm land lately, so even if the
npm publishcommand has exited, that version isn't available for everyone through npm yet.One solution for this could be to add the version to the
client_payloadof therepository_dispatchand poll in the deploy job until that version appears on npm.