8000 Seeing EMISMATCHGITHUBURL from the latest version which breaks our release build · Issue #885 · semantic-release/github · GitHub
[go: up one dir, main page]
Skip to content
8000

Seeing EMISMATCHGITHUBURL from the latest version which breaks our release build #885

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
flannanl opened this issue Jul 25, 2024 · 5 comments · Fixed by #887
Closed

Seeing EMISMATCHGITHUBURL from the latest version which breaks our release build #885

flannanl opened this issue Jul 25, 2024 · 5 comments · Fixed by #887
Labels
released

Comments

@flannanl
Copy link

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
Copy link
nandreanurag commented Jul 25, 2024 •
edited by hearts bot
Loading

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
Copy link
Author
flannanl commented Jul 25, 2024 •
edited by hearts bot
Loading

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
Copy link
Contributor
jedwards1211 commented Jul 25, 2024 •
edited by hearts bot
Loading

@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.

@jedwards1211 jedwards1211 mentioned this issue Jul 25, 2024
Merged
@jfairley
Copy link
jfairley commented Jul 26, 2024 •
edited by hearts bot
Loading

SAME!

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

@gr2m gr2m mentioned this issue Jul 26, 2024
Merged
@gr2m gr2m closed this as completed in #887 Jul 26, 2024
@github-actions GitHub Actions
Copy link

🎉 This issue has been resolved in version 10.1.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Revert "fix: failing release due to renamed repository (#878)" semantic-release/github
4 participants
@jfairley @jedwards1211 @flannanl @nandreanurag
0