0

Packagist does not support package renaming, and the official procedure is rename it in composer, resubmit and abandon the old one.

If the old package is abandoned, why it keeps auto-updating versions with new releases from GitHub? Is there a way to avoid it?

CarlosAS
  • 654
  • 2
  • 10
  • 31
  • Please share more details. What do you mean by "auto-updating", and how is that related to Composer (which is only the program to download packages)? – Nico Haase May 10 '20 at 12:31
  • The hook that keeps updating the Packagist information every time there is a new release on GitHub. Composer is just the tool in between, I will remove the tag. – CarlosAS May 11 '20 at 13:06
  • If the package is abandoned, why are there new versions published? Is the same package name, or the same repository, still in use? – Nico Haase May 11 '20 at 13:08
  • As I mentioned in the question, I'm doing a package renaming. Abandoning and resubmitting with a different name is the official way. – CarlosAS May 12 '20 at 15:21

0 Answers0