🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

We are using this in Github CI action. And below errors are identified.

/home/runner/work/_actions/snyk/release-notes-preview/v1.6.2/dist/index.js:3299
      had_error(new Error('Remote end closed socket abruptly.'))
                ^

Error: Remote end closed socket abruptly.
    at TLSSocket.on_socket_end (/home/runner/work/_actions/snyk/release-notes-preview/v1.6.2/dist/index.js:3[29](https://github.com/splunk/splunk-connect-for-syslog/actions/runs/5386296898/jobs/9776195324?pr=2079#step:4:30)9:17)
    at processTicksAndRejections (node:internal/process/task_queues:78:11)

Could you please help us with the resolution?

to help notice cases where the commit message is broken (feat:egg is a thing results in unknown prefix feat:egg treating it as misc), post a message regardless of whether or not a release will take place. this will help identify scenarios where the commit message is broken accidentally.

For my usage I'd only really care about the output on the PR, so it would be useful to have a with option that disables the confirmation check.

Hi, I love the idea behind this action. However, it's unusable (too much spam, and not so much relevant) when your workflow consists of adding more commits, squashing the commits, etc;. as soon as your workflow is different from "pushing only 1 commit"

What do you think about adding an option (can be opt-it) to either update existing comments or cleaning the old ones?

thank you

Tried 1.6.2 and it didn't seem to work I had a line (feat(play): test) which should have generated notes for that and it didnt post anything to the PR.

processing line: ea19f82 feat(play): test
adding "test (ea19f82)" to others

The actual beta release notes were created, however:

I am getting the below exception when running the action in one of my repos.

Run snyk/[email protected]
(node:1774) UnhandledPromiseRejectionWarning: ChildProcessError: git describe --abbrev=0 --tags origin/master failed with code 128
at ChildProcess. (/home/runner/work/_actions/snyk/release-notes-preview/v1.6.1/dist/index.js:2102:23)
at ChildProcess.emit (events.js:210:5)
at maybeClose (internal/child_process.js:1021:16)
at Socket. (internal/child_process.js:430:11)
at Socket.emit (events.js:210:5)
at Pipe. (net.js:659:12)
(node:1774) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1774) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.