semantic-release: Scoped Package failing to publish release notes

I’m preparing to give a training that includes semantic-release and I’m struggling to get things working well with a scoped package. Here’s my test repo and the corresponding travis build. In the build, you’ll see the output:

semantic-release ERR! post Failed to publish release notes. { [Error: {"message":"Validation Failed","errors":[{"resource":"Release","code":"custom","field":"tag_name","message":"tag_name is not a valid tag"},{"resource":"Release","code":"custom","message":"Published releases must have a valid tag"},{"resource":"Release","code":"invalid","field":"target_commitish"}],"documentation_url":"https://developer.github.com/v3/repos/releases/#create-a-release"}]
semantic-release ERR! post   message: '{"message":"Validation Failed","errors":[{"resource":"Release","code":"custom","field":"tag_name","message":"tag_name is not a valid tag"},{"resource":"Release","code":"custom","message":"Published releases must have a valid tag"},{"resource":"Release","code":"invalid","field":"target_commitish"}],"documentation_url":"https://developer.github.com/v3/repos/releases/#create-a-release"}',
semantic-release ERR! post   code: 422 }

You’ll notice from the commits that I’ve tried quite a few different things. At first I didn’t realize that this was a post error. I thought that it wasn’t actually publishing versions, but then I realized that it is indeed publishing versions, but it’s not publishing release notes to GitHub.

Any idea what the problem is here? The default tag for releases is latest which is what I want. Help appreciated!

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 8
  • Comments: 18 (4 by maintainers)

Most upvoted comments

Still is an issue. 😦

I don’t think this is an issue any longer.

Thanks, I’ll see if I can help on this, I like this tool and I’d be happy to see it generating the changelogs.

oh… that’s weird. i just tagged on another commit that made it work. maybe is was that i was not in the proper directory? go figure.

I fixed it by changing the tag version: tag: ver-${{ github.sha }}

Experiencing the same issue. I have a private repo and I didn’t want to publish my package on npm. So I have removed the npm publish command from the semantic-release script. Could that be causing any issue?