delete-package-versions icon indicating copy to clipboard operation
delete-package-versions copied to clipboard

Packages are not deleted despite the success message being returned

Open grzegorzkrukowski opened this issue 2 years ago • 10 comments

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.

grzegorzkrukowski avatar Aug 16 '22 14:08 grzegorzkrukowski

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

image

AJ-7885 avatar Sep 13 '22 21:09 AJ-7885

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.

csaba-kovacs avatar Sep 17 '22 19:09 csaba-kovacs

https://github.com/actions/delete-package-versions/issues/74 seems related to this and the real cause of the problem

peter-at-work avatar Oct 29 '22 00:10 peter-at-work

Bump!

csaba-kovacs avatar Nov 24 '22 10:11 csaba-kovacs

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

KennyKYLam avatar Nov 30 '22 19:11 KennyKYLam

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.

nadesu avatar Dec 01 '22 08:12 nadesu

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

AJ-7885 avatar Dec 01 '22 08:12 AJ-7885

Just checking, by chance is this resolved?

NeelimaShrm avatar Aug 29 '23 14:08 NeelimaShrm

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

joseenriquedevathand avatar Mar 06 '24 04:03 joseenriquedevathand

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?

peter-at-work avatar Mar 06 '24 04:03 peter-at-work