New POST endpoint to update the metadata package

[Digitalone1]

This was quickly discussed on Discord and here we can go more in details.

If an author makes a mistake in the metadata info, the only way to fix is pushing a new version. I'm not talking about something big like the tag, but a small type in the readme, for example. Or other extra details, like a missing word in the keywords.

For these things making a brand new version is overkill. On GH it could be easily fixable (I think, maybe deleting the release a making a new one with the same tag). But here on the beckend it's different.

So I'd say to introduce a new endpoint for only updating the package json on the latest version.

Obviously, since this takes place on the latest version, the upgrade will be denied if the version returned by GH does not match the latest version tag in the database.

What do you think?

[confused-Techie]

I'd be happy to implement an endpoint like this. Really maybe it could even just be under /api/packages/:packageName/refresh where it updates the Readme and package.json of your package? Think that'd be a good place for it?

[confused-Techie]

Then all we would have to do, is check the version in the new package.json is the same as whatever we have as the latest tag on the backend, and that you have proper authentication over this package, then we should be good to go