Unpublish NPM versions

[petertonysmith94]

Summary

Work was carried out to improve the functionality around unpublishing package versions (#2495):

• Allow the passing of a particular version.
• Show a more appropriate message on dry runs.

Due to issues with our package hierarchy (outlined here), we couldn't unpublish these versions automatically. Once we have migrated to a single fuels package (#2493), we should revisit this functionality to see if unpublishing is possible.

After we can confirm this functionality, we should contact support to clean up old NPM versions that are more than 72 hours old.

---

• Blocked by Consider merging all packages into fuels #2493
• Related to Consider auto-publishing workflow for every PR #2119

[petertonysmith94]

It looks like unpublishing is unreliable/does not work for our use-case.

TL;DR:
As we have many packages, all dependant upon one another, I believe we fail to meet the conditions outlined here.

Less than 72 hours ago

I was unsuccessful in unpublishing with the version 0.0.0-pr-2543-20240618113822 which was published < 30 minutes.

More than 72 hours ago

I believe we could contact support to clean up old NPM versions. We could do this once we migrate to a single package fuels package (#2493), so we have minimal dependants.

[petertonysmith94]

I believe we should stop publishing (to NPM) on every E2E test.

Looking over possible solutions:

• We could publish to a local registry using local-npm within the CI.
• Separate our testing packages (fuels-beta) from our official packages (fuels). Potentially this could be private.

Any thoughts @arboleya?

[arboleya]

Yes, let's do that and stop publishing PRs automatically.

When we merge a PR to master, we publish an update to the next tag.

We could move our npm installs fuels@next checks to happen at this point.

This way, we can stop publishing PRs while keeping the validation.

[petertonysmith94]

That's a better solution!

[petertonysmith94]

Yes, let's do that and stop publishing PRs automatically.

When we merge a PR to master, we publish an update to the next tag.

We could move our npm installs fuels@next checks to happen at this point.

This way, we can stop publishing PRs while keeping the validation.

I've implemented this in #2489.

What do you think about contacting support for cleaning up our old versions?
Happy to create a list of the versions that need cleaning.

Otherwise - is it worth updating the description and changing priority?

[arboleya]

Considering the CDN thing was addressed, should we close this?

[petertonysmith94]

@arboleya I think given the constraints that NPM has, we won't be able to unpublished until #2493 is concluded. For that reason, I'll close this until we have that resolved, then can could potentially revisit this.