Added Release pipeline action

[oscerd]

Fixes #746

[lordrip]

Awesome, thanks @oscerd.

I have a couple of questions that I would like to ask:

1. The current order is tag-and-release, npm-release, container-image-release, I wonder if it would make sense to start with the npm-release first, this way, if we try to release a broken commit by accident, this build step will fail, hence preventing the container and the release to be generated.

2. We build the project a few times in different workflows, if we wanted to avoid redefining the build process in all of them, would be a custom action the way to go?

[oscerd]

Awesome, thanks @oscerd.

I have a couple of questions that I would like to ask:

1. The current order is tag-and-release, npm-release, container-image-release, I wonder if it would make sense to start with the npm-release first, this way, if we try to release a broken commit by accident, this build step will fail, hence preventing the container and the release to be generated.

Yes, we can simply switch

2. We build the project a few times in different workflows, if we wanted to avoid redefining the build process in all of them, would be a custom action the way to go?

We can define a build action and we could re-use it from other workflow by having that defined as custom action