Test npm package availability on CI

[piotr-roslaniec]

Type of PR:

• Other

Required reviews:

• 1

What this does:

• Checks whether @nucypher/taco has a correct build available under expected npm tags

Why it's needed:

• To catch bad builds and tagging issues

[netlify[bot]]

✅ Deploy Preview for taco-demo canceled.

Name	Link
🔨 Latest commit	147b09d3817bdefd144fb648f87c4db50bd4cae8
🔍 Latest deploy log	https://app.netlify.com/sites/taco-demo/deploys/661ad7fab40e8b0008d3b074

[netlify[bot]]

✅ Deploy Preview for taco-nft-demo canceled.

Name	Link
🔨 Latest commit	147b09d3817bdefd144fb648f87c4db50bd4cae8
🔍 Latest deploy log	https://app.netlify.com/sites/taco-nft-demo/deploys/661ad7faf37290000814c3ba

[piotr-roslaniec]

We are publishing packages manually (Codechecks will work great after we release 1.0.0: https://github.com/nucypher/taco-web/pull/460). So having to run this job is just one more thing we need to remember to do.

NPM tags can also change without publishing a new version. For example, a change on lynx followed by a change on tapir will require us to release a new version for lynx and then tag it again for tapir.

It doesn't make a huge difference to me whether this job runs every hour or every 24 hours. I think the sooner we catch this the better. If we do this every 24 hours then we spend 24 less compute, but I don't think compute spent is an issue.

[manumonti]

Got it, thanks! it makes more sense to me now.