Skip to content

fix: use no-guess-dev version scheme to avoid .post0 suffix#108

Merged
sameeul merged 1 commit intoPolusAI:masterfrom
sameeul:fix/version-postfix-issue
Mar 18, 2026
Merged

fix: use no-guess-dev version scheme to avoid .post0 suffix#108
sameeul merged 1 commit intoPolusAI:masterfrom
sameeul:fix/version-postfix-issue

Conversation

@sameeul
Copy link
Member

@sameeul sameeul commented Mar 18, 2026

Change from 'post-release' to 'no-guess-dev' version scheme to ensure clean version numbers on release tags. The 'post-release' scheme was adding .post0 suffix to release versions.

With 'no-guess-dev':

  • On exact tag: returns clean version (e.g., 2.2.1)
  • After tag: keeps the tag version (e.g., 2.2.1)

This ensures PyPI releases have clean version numbers like '2.2.1' instead of '2.2.1.post0'.

Also removed unnecessary git_describe_command override.

Change from 'post-release' to 'no-guess-dev' version scheme to ensure
clean version numbers on release tags. The 'post-release' scheme was
adding .post0 suffix to release versions.

With 'no-guess-dev':
- On exact tag: returns clean version (e.g., 2.2.1)
- After tag: keeps the tag version (e.g., 2.2.1)

This ensures PyPI releases have clean version numbers like '2.2.1'
instead of '2.2.1.post0'.

Also removed unnecessary git_describe_command override.
@sameeul sameeul merged commit 71d1293 into PolusAI:master Mar 18, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant