Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I remove old versions of my package ? #1377

Closed
SeymaAkdoganRepalogic opened this issue May 16, 2023 · 7 comments
Closed

How can I remove old versions of my package ? #1377

SeymaAkdoganRepalogic opened this issue May 16, 2023 · 7 comments

Comments

@SeymaAkdoganRepalogic
Copy link

I can't remove old versions of my package. e.g. I uninstall v1.0 but it comes back when I refresh the page.

@stof
Copy link
Contributor

stof commented May 16, 2023

You need to remove the tag from Github if you don't want it to re-appear.

@SeymaAkdoganRepalogic
Copy link
Author

SeymaAkdoganRepalogic commented May 16, 2023

But before i could only remove from packagist. When the user ran the "composer require packageName" command, the last version was being installed. Why it doesn't work like that now ?

@stof
Copy link
Contributor

stof commented May 16, 2023

Well, if you only remove it from Packagist, it will be re-added automatically the next time Packagist updates your package from GitHub. This has always been the case. What might be different now is whether an update is triggered or no for your package.

@SeymaAkdoganRepalogic
Copy link
Author

I just refresh the page without updating my package. And the deleted versions are coming back.

@stof
Copy link
Contributor

stof commented May 16, 2023

Well, package updates can be triggered automatically, not just manually. Maybe packagist now automatically triggers an update after deleting versions (and for sure, if you have the github hook enabled, any push to your repo will trigger an update).

@SeymaAkdoganRepalogic
Copy link
Author

Got it. Thank you for the information

@Seldaek
Copy link
Member

Seldaek commented May 25, 2023

There was a permission bug it should work again now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants