codejedi365

I use a bash conditional around the `--unshallow` command because of the failure that @daniel-albuschat mentioned above. Happens with small repositories under 50 commits (50 is the default fetch depth...

@cfxegbert, it's a good thing to note for others. Do you know which version of GitLab that was introduced? I feel like it was pretty recent. Also can you validate...

> The GIT_ variables have been available for several years. I've been using it for over 3 years. I haven't tried to solve this problem in over 3 years so...

Well there's a million ways to solve everything and I chose git rather than finding it in GitLab Docs.

Can you provide your configuration file contents? That error is related to the config option `semantic_release.changelog.changelog_file` value. Unless my path resolution is incorrect, I added the restriction to prevent writing...

Ok, thanks! It looks like somehow the default value is failing since you are not overriding it. Can you provide your GitHub actions job configuration? It has to do with...

Ok, it is almost certainly windows and its path resolution results. Thank you for providing that snippet. I thought you were using our GitHub Action which runs in a Linux...

### :tada: This resolution has been included in version 9.8.8 :tada: The release is available on: - [PyPi package](https://pypi.org/project/python-semantic-release/9.8.8/) - [GitHub release](https://github.com/python-semantic-release/python-semantic-release/releases/tag/v9.8.8)

I believe this is a duplicate of #912. Recommend you check out the details of that issue and then we can further discuss. Also, ~~#933~~ #993 also addresses the use...

No, not intentional. #993. Duplicate is probably the wrong word for this but I do think the solutions apply to your case. It's not a perfect fix but current expectation...