softwareversion

In software development, a software version is an identifier associated with a particular build of a software product. Version numbers enable users and systems to distinguish releases, communicate changes, and manage updates, compatibility, and support. A version typically reflects a release that can be installed, tested, or cited in documentation.

The most common scheme is semantic versioning, which uses a three-part format: MAJOR.MINOR.PATCH. Additional segments may include prerelease labels (such as -alpha, -beta, -rc) and build metadata (+build.123). In semantic versioning, MAJOR changes may break backward compatibility, MINOR introduces features that are backward compatible, and PATCH applies bug fixes. Other schemes include date-based versions and build-number schemes; some projects combine these elements.

Versioning is often tied to release management and distribution. Releases are tagged in version control systems, documented in release notes, and distributed through packaging systems. Version numbers help automate dependency resolution, enable rollbacks, and communicate the scope of changes to users and operations teams. Backward compatibility policies influence how version numbers evolve.

Lifecycle considerations include long-term support, deprecation schedules, and end-of-life timelines. Dependency management tools use version constraints to declare compatibility with other software libraries. Build pipelines may automatically derive or increment version numbers from the source tree, CI/CD metadata, or tags.

Adoption varies by ecosystem. Semantic versioning is widely used in languages and platforms such as npm, Maven, and PyPI, though some projects opt for alternative or customized schemes.