autosemver
Tools to handle automatic semantic versioning in python
Decision gist · record as of 2026-08-14
No. The package is abandoned (no maintenance since 2020-11-13, last commit 2022-07-09) and carries copyleft licensing. For new projects, consider actively maintained alternatives. Only install autosemver if you are maintaining an existing codebase already using it and cannot migrate.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires git repository with semantic version tags and/or commit messages containing 'Sem-Ver:' or '* Incompatible' markers to function; git must be installed and the package must be run from within a git repository.
- High install friction: the package is abandoned (last commit 2022-07-09, no releases since 2020-11-13) and has not been maintained for over 2100 days.
- No runtime dependencies, but the stalled maintenance status makes it a risky choice for new projects.
License · maintenance · safety
GPLv3 (copyleft) — Licensed under GPLv3 (copyleft). Any project that bundles or distributes this package must also release its source code under a compatible open-source license.
last release 2020-11-13 (2100 days) · last repo commit 2022-07-09 · 5 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 99,013 downloads/mo, #13,043 on PyPI
Alternatives
Verify before relying
pip install autosemver
# In setup.py:
setup(
name='some-package',
install_requires=['autosemver'],
setup_requires=['autosemver'],
autosemver=True,
)- Whether the package works with modern Python versions (python_support unspecified in metadata)
- Current compatibility with recent build tools and git workflows
- Whether the package's git-based version extraction still functions reliably in contemporary CI/CD environments
What it is and what it does
Autosemver is a setup.py integration tool that automatically derives semantic versions for Python packages by reading git repository metadata—tags, commit messages, and special markers like 'Sem-Ver:' or '* Incompatible'. You add a single line (autosemver=True) to your setup.py, and the tool generates version strings compliant with the semantic versioning standard without requiring manual version bumps in code.
The package has no runtime dependencies and is designed to run at build time. However, it is no longer maintained: the last commit was 2022-07-09 and the final release was 2020-11-13. For projects starting now, this represents a significant risk—there is no active support for compatibility with modern Python or build workflows, and any bugs or breaking changes in the ecosystem will not be addressed.
Use it for
- Eliminate manual version string edits in setup.py by deriving versions automatically from git history.
- Enforce semantic versioning discipline by parsing commit messages for breaking-change markers during the build process.
- Streamline build pipelines that need consistent, git-derived version numbers without extra configuration steps.
- Maintain existing projects already using autosemver when migration to other tools is not feasible.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
No.
The package is abandoned (no maintenance since 2020-11-13, last commit 2022-07-09) and carries copyleft licensing. For new projects, consider actively maintained alternatives. Only install autosemver if you are maintaining an existing codebase already using it and cannot migrate.
Install
autosemver on PyPI
Before you install
High install friction: the package is abandoned (last commit 2022-07-09, no releases since 2020-11-13) and has not been maintained for over 2100 days. No runtime dependencies, but the stalled maintenance status makes it a risky choice for new projects.
Requires git repository with semantic version tags and/or commit messages containing 'Sem-Ver:' or '* Incompatible' markers to function; git must be installed and the package must be run from within a git repository.
License in practice
Licensed under GPLv3 (copyleft). Any project that bundles or distributes this package must also release its source code under a compatible open-source license.
Quickstart
pip install autosemver
# In setup.py:
setup(
name='some-package',
install_requires=['autosemver'],
setup_requires=['autosemver'],
autosemver=True,
)Verify before relying
- Whether the package works with modern Python versions (python_support unspecified in metadata)
- Current compatibility with recent build tools and git workflows
- Whether the package's git-based version extraction still functions reliably in contemporary CI/CD environments
Package facts
| License | GPLv3 copyleft |
| Python support | Not specified |
| Install friction | High. Source build required |
| Runtime dependencies | None |
| Maintenance | Abandoned 2,100 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 99,013 / month, #13,043 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: autosemver-1.0.0.tar.gz
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “automatic semantic versioning”
- autosemverAutomatically generates semantic versions for Python packages by…
- python-semantic-releaseAutomates semantic versioning and release management for Python…
- dunamaiDunamai generates dynamic, standards-compliant version strings from…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also release-tag · vcver · semantic-version · semver · reno · python-semantic-release · setuptools-git-versioning · setuptools-scm-git-archive · bump-my-version · semver4