Packages are not deleted despite the success message being returned

[grzegorzkrukowski]

I used this action to delete over 250 packages in 3 runs due to 99 limitations per run.
Each run correctly showed 99 removals + the last one 52 - as it removed it.

But all packages are still visible in a browser when I check it here:
https://github.com/OWNER/REPO/pkgs/npm/PACKAGE_NAME/versions

Re-running the action is not removing anything anymore.

[AJ-7885]

I count the same issue it shows it is remove but when I check the published version they all remind as before.

[csaba-kovacs]

Same here, shows 6 but nothing was deleted.
Funny part, i tried another package delete method, and there it appears that the deletion went through by this action, since that method saw the number of versions i was keeping. So it didnt delete anything.. 30 versions are still in the package, but it returns data that 3 are there.

[peter-at-work]

#74 seems related to this and the real cause of the problem

[csaba-kovacs]

Bump!

[KennyKYLam]

Deleting shows success for me but the total # of packages is the same 😢 and showed no increase in deleted packages.

[nadesu]

Yes, as mentioned here, this Action does not work for npm registry atm and it throws stale results. We are actively working on getting it work again for npm registry along with container registry.

[AJ-7885]

I am try the same with Github registry and has same issue, where this should work?

[NeelimaShrm]

Just checking, by chance is this resolved?

[joseenriquedevathand]

I have the same problem here, is there any update on this problem?

[peter-at-work]

With #74 being fixed/closed starting with v4.0.0 or later of the action, this issue can also be closed. Would the OP or others provide a workflow YAML and/or run logs to look at and see if it's the same issue?