Seeing EMISMATCHGITHUBURL from the latest version which breaks our release build

[flannanl]

The latest version with the change: #878 is currently breaking our release build. We are using Travis CI to trigger our release build and we start to get EMISMATCHGITHUBURL even though our repository URL did not change. We are using Enterprise GitHub. Is there a way to show what is mismatching? We currently need to pin to version 10.1.1 to get our builds to work again.

[nandreanurag]

I believe this change only handles the package.json configuration file. If you use other configuration files like .releaserc or release.config.js, it will fail. Which configuration file are you using?

[flannanl]

I'm using the package.json. I don't have .releaserc or release.config.js in my repository. If there is a way to output the actual and the expecting repository URL, at least I have a better idea what's wrong. Right now, I have no idea what the URL looks like.

[jedwards1211]

@gr2m I can't seem to use an https:// URL as required by this new change on CircleCI:

circleci@52eb909c3fee:~/project$ git remote set-url origin https://github.com/jcoreio/zod-forms.git
circleci@52eb909c3fee:~/project$ git remote -v
origin	ssh://git@github.com/jcoreio/zod-forms.git (fetch)
origin	ssh://git@github.com/jcoreio/zod-forms.git (push)

Even if I could, according to the Git docs, this would break CI releases anyway because after changing to an HTTPS URL,

The next time you git fetch, git pull, or git push to the remote repository, you'll be asked for your GitHub username and password. When Git prompts you for your password, enter your personal access token

I think it would be better to only compare the <owner>/<repo> portion of the two URLs.

[jfairley]

SAME!

I had to list the previous version (10.1.1) in my package.json to get releases going.

[github-actions]

🎉 This issue has been resolved in version 10.1.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀