Giters

hubotio / hubot

A customizable life embetterment robot.

Home Page:https://hubotio.github.io/hubot/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

The automated release is failing 🚨

github-actions opened this issue · comments

commented

🚨 The automated release from the master branch failed. 🚨

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

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 fix 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 are some links that can help you:

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 📦🚀

commented

I can. Of course, the user that was setup for NPM goes to my old work email 😓

I will poke around and see if I can setup something.

commented

I can generate a token. I just don't have access to add it to Github.

commented

I've fixed the NPM_TOKEN. Brief outline:

  • create a new token on npmjs.com
    • chose granular token
    • read/write access
    • select the hubot packages to include (did everything on this org)
    • choose 1 yeaer
  • on github.com/hubotio
    • go to settings
    • secrets & variables
      • actions
        • add NPM_TOKEN
  • on the failed action, re-run all

It succeeds now, but doesn't seem to have made a release: https://github.com/hubotio/hubot/actions/runs/4885165266/jobs/8814350358

Digging into it a bit more still

commented

So, reading over some of the output, it really seems like it's scanning the commits, and not the PR titles. One way to make it work would be to use Squash & Rebase rather than Merge. If we enforce the title follows semantic-release's conventions, then the squash and merge would end up with a semantic commit message, and trigger it that way. I know I was the one that suggested trying to do it this way, but I forgot that we use Squash & Rebase, which is what makes it work.

Oh, I think I found it. This might help: https://github.com/marketplace/actions/conventional-pull-request ... digging in more.

commented

I'm lost because every commit message I used was "chore(release): Add semantic-release". So there's 3 commits, all with that same message. Which I thought was the correct format. What am I missing?

commented

Your guess is as good as mine at this rate. Check this out: https://github.com/hubotio/hubot/actions/runs/4885165266/jobs/8814350358

chore(release): Add semantic-release
[12:43:39 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:43:39 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(release): Add semantic-release
[12:43:39 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:43:39 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(release): Add semantic-release
[12:43:[39](https://github.com/hubotio/hubot/actions/runs/4885165266/jobs/8814350358#step:7:40) AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:43:39 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(release): Add semantic-release
[12:43:39 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:43:39 AM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: Merge pull request #1617 from hubotio/update-rest-of-dependencies

That does not seem to be the format needed. I think based on https://github.com/semantic-release/semantic-release#commit-message-format would need a commit like feat: new feature.

I think for now:

I think those things will fix it for next time 🤞🏻

commented

ah. Yes. semantic-release only creates a release if there's a commit message with feat, fix or BREAKING CHANGE, but not for commit messages with chore and this PR only has chore commit messages. Programming is so hard!

commented

The machine did the thing! v4.0.0 happened