-
Notifications
You must be signed in to change notification settings - Fork 255
Version Command failed Create Release step under Github Enterprise VCS #895
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.
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
Comments
@xesf, I'm sorry that the upgrade failed for you. Ends up we don't currently support GitHub Enterprise Server's api path at this time. I noticed this issue with the last patch update of url parsing and should be able to add support over the next week. |
Thanks for the quick reply @codejedi365 Cheers |
@xesf, since I do not have a GitHub Enterprise Server instance to test my changes with, would you be willing to try out this alpha release, I recommend running the command When you run the test, please use the following command to gather verbose logging semantic-release -vv version |
Sure, sounds good and thanks for the quick fix. I will try later today since I won't be at home for the entire day and let you know. |
@codejedi365 I've test it and it is working fine.
Not related, but I notice the new version has a different changelog default template, where it includes the |
@xesf, excellent news! Thank you for the quick response and live testing, will include the fix in the next release this weekend.
Yes, it is as of now. That was a change from v7 to v8, by the previous maintainer, where the entire commit is included in the changelog. I believe the reason was because of the use of squash commits which does not have a working solution in PSR as of yet. I have created a milestone to improve changelogs and have many changes in the works for both squash commit parsing and cleaner changelog defaults. Hopefully completed over the next month. If you want the change now, you can override the changelog with jinja2 templates. |
* test(github): adjust init test to match the Enterprise Server api url * feat(github): extend support to on-prem GitHub Enterprise Server Resolves: #895
Awesome!! Thanks for the prompt fix. Got it, it is just a small thing so not very important, I just didn't know it was on purpose. I will still have a look on how |
🎉 This issue has been resolved in version 9.5.0 🎉The release is available on: |
The problem
Semantic Release is not able to Create a Release in Github during
version
command.I am trying to migrate my setup from version 7 to 9 and re-configuring from setup.cfg file to pyproject.toml
The previous single
publish
command no longer works due to breaking changes on v9 and the newversion
is partially working.The new version is identified, changelog is updated, commits and tags pushed to github, but at the last stage semantic release is not able to create a release under github release options.
Expected behavior
Be able to create a release in VCS Github.
Environment
Running in a private Github Action Runners via command line:
python3.11 -m semantic_release version
(failed command)GHA workflow:
python 3.11
semantic release 9.4.2
via pip
Configuration
Logs
Additional context
The text was updated successfully, but these errors were encountered: