Hot-fixing the automatic release issuance workflow for npm packages yet again.
The previous fix is still believed to bo correct conceptually, there was just
a silly mistake of the mixing up of the ghcr vs npm tokens in the environment
variables that get populated from the secrets.
[x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[x] Follow the Commit Linting specification. You may refer to this link for more information.
Character Limit
[x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[x] Commit Message per line must not exceed 80 characters (including spaces and special characters).
A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.
Hot-fixing the automatic release issuance workflow for npm packages yet again. The previous fix is still believed to bo correct conceptually, there was just a silly mistake of the mixing up of the ghcr vs npm tokens in the environment variables that get populated from the secrets.
Fixes #451
Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com
Pull Request Requirements
upstream/mainbranch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.-sflag when usinggit commitcommand. You may refer to this link for more information.Character Limit
A Must Read for Beginners For rebasing and squashing, here's a must read guide for beginners.