CI fail on publish a new version

[bourgeoa]

@angelo-v I tried to publish with CI and it fails https://github.com/linkeddata/rdflib.js/runs/4278968539?check_suite_focus=true with 2 attempts. Publish is done but seem to have failed. I did :

• commit v2.2.11 : npm publish succeed but npm publish-latest fail
• following the publish-latest fail :
  • I git push origin main --follow-tags
  • then re-run all jobs CI : npm publish fail but npm publish-latest succeed

[angelo-v]

The first attempt failed in step npm-publish-latest with

npm ERR! 400 Bad Request - PUT https://registry.npmjs.org/rdflib - Must associate a single dist tag with new publishes.

https://github.com/linkeddata/rdflib.js/runs/4278938794?check_suite_focus=true#step:5:212

The second attempt failed in step npm-publish-build with

npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/rdflib - You cannot publish over the previously published versions: 2.2.11-8e780a56.

https://github.com/linkeddata/rdflib.js/runs/4278981735?check_suite_focus=true#step:7:241

The latter is quite easy to explain: Since it is the second attempt, npm refuses it, because it does not allow to publish the same version again.

Anyway, I am not sure why the first attempt failed in npm-publish-latest. Everything worked fine on first attempt in v2.2.12, so I wonder, if it was a hickup at npm side. Or do you have an explanation why v2.2.12 succeeded and v2.2.11 did not?