Skip to content

Publish NPM package #25583

Answered by juffalow
juffalow asked this question in Packages
Nov 15, 2019 · 1 comments · 1 reply
Discussion options

You must be logged in to vote

If anyone would ancounter the same problem, here is the solution:

In $GITHUB_REF env variable is reference to the release version in format “refs/tags/<tag>”. You can remove the prefix and pass the version to publish command:

run: yarn publish --new-version ${GITHUB_REF#"refs/tags/"}

It will publish the new version, but still ends with error. It is because it tries to also create a commit, but git needs your name and email to do it.

Exit code: 128
Command: git
Arguments: commit -m v2.3.16
Directory: /home/runner/work/pentest-tool-lite/pentest-tool-lite
Output:
*** Please tell me who you are.

Run
git config --global user.email "you@example.com"
git config --global user.name "Your Name"

to…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@KinNeko-De
Comment options

Answer selected
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Packages Host your dependencies, libraries, and production-ready code, right from your repository
2 participants