Versioning Glossary

Browse 35 versioning terms defined in plain English, from the cultural dictionary of computing.

35 Versioning Terms

AI Version
A specific version of an AI model, prompt set, workflow, or configuration used in evaluation or production. Explicit AI versioning is important because...
Application Version
The specific release identifier of an application build, used to distinguish deployed code, track changes, and correlate behavior with a known state of the...
Backward Compatible
Describing a change that still works with older clients, data, integrations, or assumptions rather than forcing everything to upgrade at once. Backward...
Breaking Change
A change to software that causes dependent code to stop working. Renaming a function, removing a parameter, changing a return type — anything that makes...
Build Number
A numeric or otherwise unique identifier assigned to a particular build output so it can be traced back to source, configuration, and pipeline history. Build...
Bumping Version
Informal shorthand for increasing a version number, usually during a release or dependency update. In developer slang, 'just bump the version' can make a...
Changesets
A release-management approach and popular tool that lets maintainers record versioning intent in small metadata files which are later combined into changelogs...
Code Version
A specific identified state of source code, usually represented by a commit, tag, branch point, or release identifier. Knowing the exact code version is...
Compatibility
The ability of software, data, APIs, or environments to work correctly together despite differences in version, platform, or implementation. Compatibility is a...
Deprecated
Marked as outdated and discouraged for new use, even if it still works for backward compatibility. In practice it often means 'this will become your problem...
GitHub Release
A tagged release entry on GitHub used to package release notes, binaries, source snapshots, and version milestones in a repository. It is a standard way to...
Major Version
The highest-order number in a versioning scheme, typically used to signal breaking changes or major shifts in compatibility under semantic versioning...
Minor Version
The middle segment in a semantic version number, commonly used to indicate backward-compatible new functionality without breaking existing integrations. Minor...
Model Fingerprint
An identifier or signature used to distinguish a specific model build, configuration, or inference environment from others. Model fingerprints help trace...
Model Version
A specific version of a model distinguished from earlier or later versions by weights, configuration, or release status. Explicit model versioning is essential...
Package Version
The version identifier assigned to a package release. In package ecosystems, package versions are critical for dependency resolution, upgrade behavior,...
Patch Level
The current update or remediation state of a system, application, or device relative to the latest relevant patches. Knowing patch level helps security teams...
Point Release
A small release, usually reflected in the final segment of a version number, intended to deliver bug fixes, minor improvements, or maintenance updates without...
Prompt Registry
A registry used to store, version, and track prompts and related metadata such as owners, evaluations, and rollout status. Prompt registries help teams treat...
Prompt Versioning
The practice of assigning explicit versions to prompts so changes can be tracked, compared, rolled back, and audited. Prompt versioning is especially important...
Public API
The set of functions, classes, endpoints, or interfaces that a library, module, or service explicitly exposes for external consumers to use, as opposed to...
Release Channel
A named distribution track (such as stable, beta, canary, or nightly) that determines which version of software a user receives, allowing teams to ship...
Release Cycle
The full sequence from planning and development through testing, packaging, and publication of a software version. Teams discuss release cycles to reason about...
Release Strategy
The intentional plan for how a project versions, packages, stages, communicates, and rolls out software changes over time. Release strategy includes decisions...
Release Tag
A version tag in version control marking the exact commit associated with a release. In repository practice, release tags make it easy to trace distributed...
Rolling Release
A release model where software is updated continuously rather than through large, infrequent version jumps. Rolling releases give users faster access to...
Semantic Release
A release automation approach where commit messages or merged changes determine version bumps, changelogs, and publication behavior according to semantic...
Semantic Versioning
A versioning scheme using MAJOR.MINOR.PATCH (e.g., 2.4.1) where MAJOR = breaking changes, MINOR = backwards-compatible features, PATCH = backwards-compatible...
Semantic Versioning
A versioning scheme (MAJOR.MINOR.PATCH) where MAJOR indicates breaking changes, MINOR adds backwards-compatible features, and PATCH fixes bugs. Enables...
Semver Convention
The convention of using semantic versioning rules, where version numbers communicate whether a release contains breaking changes, backward-compatible features,...
Update Hell
A painful state where upgrades are blocked by cascading dependency issues, breaking changes, and incompatible version requirements. It is especially common in...
Upgrade Path
The supported route by which users or systems can move from one version, tier, or architecture to another with acceptable risk. Good products make the upgrade...
Version Bump
A change that increments a project’s own version number or updates the version of a dependency it uses. Version bumps can be mechanically simple but...
Versioning Strategy
The overall approach a project takes to numbering releases and signaling compatibility, stability, or lifecycle stage to users. A versioning strategy may use...
Version Policy
The documented rules a project uses to decide when and how version numbers change, how long versions are supported, and what compatibility promises they imply....

Related Topics