codejedi365

After reviewing your logs, this does not look like a semantic-release problem. When semantic-release runs your build command, you have a number of errors that happen. First, pip throws errors...

@bdraco, my mistake, I think I was looking at the wrong job / pipeline earlier. Yes, good job finding a solution. I didn't write the GitHub Action and I didn't...

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

Good catch! I thought I had resolved this but I guess not completely. Yes, `--strict` is exactly there for that reason. An alternative if you don't like a failed job...

One problem with this is that if it fails for some other reason (an exception is thrown or auth fails), the exit code is squashed and the job succeeds I...

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

can confirm this is an issue on Mac as well, I've started narrowing down this issue but still no reliable fix. It seems to be a race-condition for when the...

The primary tests in question that cause all my errors are `test_algorithm_no_zero_dot_versions_scipy` and the other `test_algorithm_with_zero_dot_versions_scipy`. @relekang you can comment these out and it all runs. @bernardcooke53, I will try...

Ah! It works! I would have never thought of that. Thanks!

> I feel this is a hack. I think the tests should be refactored avoid the use of `lazy_fixture` and allow to parametrize them. Oh, I don't think anyone is...