expenditure
in English: release
A release is a finalized, version-numbered state of a software or AI model that the creators officially hand over to users.
In plain terms
Software is never fully finished: developers improve and expand it day by day. A release is the moment when they say: this state is good enough now, we will give it to people. It gets a version number, and from then on it can be referenced precisely.
It is like book publishing. The author could polish the manuscript indefinitely, but eventually it must be sent to the printer. What goes on sale is the first edition; errors are corrected later in a revised second edition. The copy on your shelf does not change as a result. With software it is partly different: a program installed on your machine changes only when updated (often automatically), while online services are replaced by their creator on its own servers, so there is nothing for you to do.
The same logic applies in the AI world. A language model, a chat application, or a coding agent is released in versions, which is why the same tool might behave slightly differently from one week to the next.
The release is therefore not the work itself, but its fixed, numbered snapshot. This makes it possible to track what has changed and to revert to a previous, working state in case of issues.
How it works
- Developers gather completed new features and bug fixes, then decide what goes into the next release and what is deferred.
- The selected state is tested: first with automated checks, then often in a narrower scope, as a preliminary (beta or release candidate) version.
- The state receives a version number, for example 2.4.1. The numbers usually indicate the scale of the change: a major overhaul, a new feature, or just a bug fix.
- The release notes are prepared, listing what is new, what has improved, and what functions differently compared to the previous version.
- The release is published: it goes into the app store, onto the download page, or onto the service's servers. Often gradually, first to only a small portion of users.
An everyday example
In the morning, your phone notifies you that your banking app has been updated, and you see this in the description: "version 3.12: faster login, bug fixes." This is a new release. The same happens when you read in the news that a company has released a new version of its language model.
Who is affected
A common misconception
Limits and risks
- Release is not a guarantee of flawlessness: testing only filters out some errors, while the rest emerge during actual use.
- Support for older versions eventually ends, and from that point on, they receive no security updates, making their use risky.
- With AI models, a new release may give a different answer to the same question, so what worked yesterday must be rechecked after switching.
- The size of the version number does not always indicate the extent of changes, because marketing considerations often influence the numbering.
Similar, but not the same
- deployment – Installation is a technical step that puts the program on the server; release is the decision that users will actually receive it.
- version – A version can be any intermediate state of the software, but a release is only what is officially published.
- update – An update is how the new state replaces the old on your device; a release is what the creator publishes, and to which you can update.
Related concepts
software development, software lifecycle
beta version, release candidate, bug-fix release, long-term support release
version control, installation, update, release notes, continuous delivery
A brief history
The software release practice originates from the mainframe era: manufacturers already delivered programs in numbered releases on magnetic tape in the 1960s. Later, new versions of boxed programs reached stores on discs. The principle of "release early and often" was made widely known by Eric S. Raymond's 1997 essay, The Cathedral and the Bazaar; today, many services release new versions several times a day.
Where things stand
At the end of 2026, a release is a basic concept in the software industry, and most of the process is automated. Because AI models and agents are released in rapid succession, you also come across the term regularly in everyday news.
In the news
- GitHub Copilot impact dashboard adds chat and VS Code agent usage, code review gets API controlsNov 6, 2026 · Code
- GitLab 19.5 makes agentic development a governed part of its DevOps platformNov 6, 2026 · Code
- Equinix plans $7 billion capex push and bets on smaller facilitiesNov 6, 2026 · Ipar
- Almost half of Visa's AI shopping agent test runs failNov 5, 2026 · Marketing
- Visa test: AI shopping agents failed 42.8% of runsNov 5, 2026 · Money
- India releases its own foundation models as South Korea sets a record budget for sovereign AINov 2, 2026 · Agent Age
- Hungarian survey: 58% of shoppers use AI for shopping, and trustworthiness is decisiveNov 2, 2026 · Marketing
- Android Studio opens to any AI coding agent, ending Gemini exclusivityNov 2, 2026 · Code
Also known as
expenditure · release · software release · version release · Appearance · software release
Sources
This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.