create ci check to verify that new added versions exist

[NachoVazquez]

What is the motivation/use case for changing the behavior?

Once a new version is added or a change is made to the existing version there is no check to verify if the action truly exists.

Describe the solution you'd like

I think it would be interesting to perform a fetch to npm and verify that each version exists.

This could be made directly using a script or using some custom or pre-existing GH Action

Describe alternatives you've considered

• create a full package.json, set the CI with a matrix to override the version and run an npm i

Additional context

UPDATE:

Currently we are not protected against adding or modifying packages versions that don't exist.

For example, if adding Angular 13 support and using the wrong version for @angular/cli, anyone using our action will see the action fail because the provided version does not exist.

With the suggested check we at least verify that the versions of the packages are valid.

[LayZeeDK]

Please elaborate. I don't understand this issue.

[NachoVazquez]

I added an update