The version parameter of this action is actually the release field in the Sentry init config. This naming mismatch is confusing and particularly interesting since https://docs.sentry.io/platforms/javascript/#configure suggests prefixing your releases with a projectname. If the names are inconsistent, the releases will not work properly and debugging is kind of hard due to the behavior of releases in Sentry (shown below). The appropriate naming is non-obvious from the documentation and slightly weird for a version parameter.

The releases tab seems to auto-generate releases for incoming errors, so it will show both versions making it appear the correct one was created.

However diving into a project's source maps (that page is kind of hidden) will show the versions twice, one without source maps (as also apparent in errors if your server is blocking HTTP access to sourcemaps):

Only the tooltip will reveal the true release name (the other has no prefix):

I would suggest adding a release or release-name parameter and deprecating version or hiding it in the docs for clarity.