change-wheel-version
Change the version of a wheel file
Decision gist · record as of 2026-08-14
Yes, if you need to modify wheel metadata after build time. Low install friction and no known vulnerabilities make it safe to try. However, dormant maintenance status (701 days since last release) and small user base suggest limited real-world validation—test thoroughly on your wheel format before relying on it in production.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python >=3.9
- Low install friction with three lightweight runtime dependencies.
- Maintenance is dormant—last release was 701 days ago—but the repository is not archived and targets current Python versions.
License · maintenance · safety
(unclear)
last release 2024-09-12 (701 days) · last repo commit 2024-09-12 · 2 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 197,852 downloads/mo, #9,745 on PyPI
Alternatives
Verify before relying
pipx run change_wheel_version some.whl --local-version special.build.info- Whether modifying wheel metadata preserves digital signatures or integrity checks on the wheel file.
- Whether the tool handles all wheel formats and edge cases (e.g., namespace packages, entry points).
- Real-world adoption and whether dormant status reflects stability or abandonment.
What it is and what it does
change_wheel_version is a command-line tool that rewrites the version string in a wheel file's metadata after the wheel has already been built. It works by modifying the version in the package metadata without requiring a rebuild of the package itself. This is useful when you have a pre-built wheel and need to tag it with a local version identifier or adjust its version for distribution purposes.
The tool depends on wheel, installer, and packaging to handle the low-level wheel format operations. It requires Python >=3.9. Because it only touches packaging metadata and not version strings embedded in source code, it is not a substitute for proper versioning during the build process, but rather a post-hoc adjustment mechanism for already-compiled artifacts.
Use it for
- Add a local version suffix to a custom-built wheel for internal or CI/CD distribution without rebuilding.
- Adjust the version of a pre-built wheel to match a different release tag or deployment environment.
- Patch the version metadata in a wheel artifact when the original build process cannot be easily re-run.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need to modify wheel metadata after build time.
Low install friction and no known vulnerabilities make it safe to try. However, dormant maintenance status (701 days since last release) and small user base suggest limited real-world validation—test thoroughly on your wheel format before relying on it in production.
Install
change-wheel-version on PyPI
Before you install
Low install friction with three lightweight runtime dependencies. Maintenance is dormant—last release was 701 days ago—but the repository is not archived and targets current Python versions.
Requires Python >=3.9
Quickstart
pipx run change_wheel_version some.whl --local-version special.build.infoVerify before relying
- Whether modifying wheel metadata preserves digital signatures or integrity checks on the wheel file.
- Whether the tool handles all wheel formats and edge cases (e.g., namespace packages, entry points).
- Real-world adoption and whether dormant status reflects stability or abandonment.
Package facts
| License | Not declared unclear |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 3 packageswheelinstallerpackaging |
| Maintenance | Dormant 701 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 197,852 / month, #9,745 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: change_wheel_version-0.6.0-py3-none-any.whl
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 › “modify wheel version”
- change-wheel-versionModifies the version metadata in an already-built wheel file without…
- wheelA command-line tool for inspecting, converting, and modifying Python…
- patchelfProvides a PyPI-packaged binary of patchelf, a utility for modifying…
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 wheel · patchelf · delvewheel · auditwheel · check-wheel-contents · repairwheel · editables · distlib · whey · runtime-builder