Retagging and repushing old tags, breaking apps which are using CDN

[zerdos]

...or apps which are using npm.
for example, bundle is missing from here,
https://unpkg.com/browse/[email protected]/dist/
but it was available a couple of hours ago.

Also noticed this a couple of weeks ago, with the message-port-client package, that time I had a build faulure - the same tag was reused with the latest failed build.

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[xmaysonnave]

ipfs-http-client is also unavailable from jsdelivr...
https://cdn.jsdelivr.net/npm/[email protected]/dist/index.min.js
Thanks

[achingbrain]

Minified bundles were being built in a pre-build step, but then the 'prepare' scripts were being run that deleted the dist folder before publishing. Oops.

Updated versions have been published, please try again with [email protected] and [email protected].

the same tag was reused with the latest failed build.

I'm not sure this is possible, npm doesn't let you reuse versions and jsdelivr/unpkg etc pull from npm.

bundle is missing from here, unpkg.com/browse/[email protected]/dist but it was available a couple of hours ago.

[email protected] has only just been published - the bundle was available for the previous version, maybe that's what you pulled down last time?