Invalid call to git-mkver

[thclark]

Bug report

What is the current behavior?

I've updated the release, because I needed to use a version of poetry compatible with the latest pyproject.toml standard.

I made the release (1.0.1) and am now getting the following error when running:

/usr/bin/docker run --name octuechecksemanticversion101_077300 --label 1af1a0 --workdir /github/workspace --rm -e "INPUT_PATH" -e "INPUT_BREAKING_CHANGE_INDICATED_BY" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e
[2024-07-25 11:23:5[6](https://github.com/octue/amy/actions/runs/10092701070/job/27908459394#step:4:7),040 | INFO | check_semantic_version.check_semantic_version] Getting current version from '/github/workspace/pyproject.toml'.
[2024-07-25 11:23:56,[7](https://github.com/octue/amy/actions/runs/10092701070/job/27908459394#step:4:8)32 | WARNING | check_semantic_version.check_semantic_version] No `mkver.conf` file found. Generating one instead.
Traceback (most recent call last):
  File "/usr/local/bin/check-semantic-version", line [8](https://github.com/octue/amy/actions/runs/10092701070/job/27908459394#step:4:9), in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/cli.py", line 30, in main
    match = check_versions_match(args.path, args.breaking_change_indicated_by)
  File "/usr/local/lib/python3.[10](https://github.com/octue/amy/actions/runs/10092701070/job/27908459394#step:4:11)/site-packages/check_semantic_version/check_semantic_version.py", line 57, in check_versions_match
    expected_semantic_version = _get_expected_semantic_version(
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/check_semantic_version.py", line 141, in _get_expected_semantic_version
    raise CalledProcessError(returncode=e.returncode, cmd=e.cmd, output=e.output, stderr=e.stderr) from None
check_semantic_version.check_semantic_version.CalledProcessError: Command '['git-mkver', '-c', '/tmp/tmpkh_32qvh', 'next']' returned non-zero exit status 1. Stderr: b''

What is the expected behavior?

Should work as normal

Other information

https://github.com/octue/amy/actions/runs/10092701070

[cortadocodes]

I've just experienced the same

[2024-08-05 13:24:07,174 | INFO | check_semantic_version.check_semantic_version] Getting current version from '/github/workspace/pyproject.toml'.
[2024-08-05 13:24:0[7](https://github.com/octue/octue-sdk-python/actions/runs/10249688477/job/28353638109#step:4:8),814 | WARNING | check_semantic_version.check_semantic_version] No `mkver.conf` file found. Generating one instead.
Traceback (most recent call last):
  File "/usr/local/bin/check-semantic-version", line [8](https://github.com/octue/octue-sdk-python/actions/runs/10249688477/job/28353638109#step:4:9), in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/cli.py", line 30, in main
    match = check_versions_match(args.path, args.breaking_change_indicated_by)
  File "/usr/local/lib/python3.[10](https://github.com/octue/octue-sdk-python/actions/runs/10249688477/job/28353638109#step:4:11)/site-packages/check_semantic_version/check_semantic_version.py", line 57, in check_versions_match
    expected_semantic_version = _get_expected_semantic_version(
  File "/usr/local/lib/python3.10/site-packages/check_semantic_version/check_semantic_version.py", line 141, in _get_expected_semantic_version
    raise CalledProcessError(returncode=e.returncode, cmd=e.cmd, output=e.output, stderr=e.stderr) from None
check_semantic_version.check_semantic_version.CalledProcessError: Command '['git-mkver', '-c', '/tmp/tmplozkndcm', 'next']' returned non-zero exit status 1. Stderr: b''

[cortadocodes]

Currently at a loss as to why version 1.0.3 doesn't fix this