chore(cd): update cd workflow

[joshua-goldstein]

• Use appropriate token name with granular access
• Specify whether release is latest, beta, or rc (without this it will always default to latest)

[kevinmingtarja]

LGTM! Just one clarification regarding the token secret name change.

[joshua-goldstein]

LGTM! Just one clarification regarding the token secret name change.

Thanks for the quick review. The problem actually was with the token (either it was out of date or expired). I regenerated the token and it was published successfully to npm. The error message was just misleading.

However I noticed a different problem. :) Without specifying the version, it defaults to latest, which we do not want in the case of an rc like this. I added a field in the workflow to make this optional.

[kevinmingtarja]

LGTM! Just one clarification regarding the token secret name change.

Thanks for the quick review. The problem actually was with the token (either it was out of date or expired). I regenerated the token and it was published successfully to npm. The error message was just misleading.

However I noticed a different problem. :) Without specifying the version, it defaults to latest, which we do not want in the case of an rc like this. I added a field in the workflow to make this optional.

Ah i see, sounds good Josh. And yeah it makes sense to have the option for tags. LGTM!