add npm token for semantic release process as repo secret
alexandercbooth opened this issue · comments
This is done now.
Thanks for adding @captainsafia! Looks like there was an issue with a mismatch of already published versions preventing a new release. I'll check into this tonight.
It seems like the issue was semantic-release getting the version from the git tags, which were behind the published version on npm. I apologize for pushing directly to master, but I just wanted to trigger the release once I updated the tags. A new version was released with that last commit and it looks like it's all set now.
@alexandercbooth No worries -- I actually just forgot that having the git tag was another requirement for this. Thanks for the follow-up.
@captainsafia No problem-- I'll tackle some of the others next 👍