Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions reference/fleet/fleet-agent-release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,12 @@ products:

# {{agent}} release process [fleet-agent-release-process]

## Scheduled releases

{{agent}} follows a release process aligned with the broader {{stack}} release schedule. The latest features, enhancements, and fixes are documented in the [release notes](../../release-notes/fleet-elastic-agent/index.md).

## Independent agent release
## Independent {{agent}} releases

The independent agent release (IAR) is a hotfix release process for {{agent}} and {{elastic-defend}}, designed to deliver critical fixes and updates independently of the full stack release. The IAR process is more conservative than a typical patch release, and only modifies the specific {{agent}} components needed for a targeted fix. For example, an IAR hotfix release for {{elastic-defend}} would only change the endpoint-security executable, with the remaining executables being exactly those released in the previous patch.
Independent {{agent}} releases deliver critical fixes and updates for {{agent}} and {{elastic-defend}}, independently of the full stack release. This is a more conservative process than a typical patch release, and only modifies the specific {{agent}} components needed for a targeted fix. For example, an independent {{agent}} hotfix release for {{elastic-defend}} would only change the endpoint-security executable, with the remaining executables being exactly those released in the previous patch.

The IAR version format appends a build identifier in the format `+build{yyyymmddhhmm}` to the semantic version it is based on, where `{yyyymmddhhmm}` is the release timestamp of the build.
In independent {{agent}} releases, the version format appends a build identifier in the format `+build{yyyymmddhhmm}` to the semantic version it is based on, where `{yyyymmddhhmm}` is the release timestamp of the build.
2 changes: 1 addition & 1 deletion reference/fleet/upgrade-elastic-agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ With the right [subscription level](https://www.elastic.co/subscriptions), you c

3. In the Upgrade agent window, select or specify an upgrade version and click **Upgrade agent**.

{{kib}} provides a list of the {{agent}} versions available for upgrade. A version number ending with a build identifier in the format `+build{yyyymmddhhmm}` indicates an [independent agent release version](./fleet-agent-release-process.md#independent-agent-release).
{{kib}} provides a list of the {{agent}} versions available for upgrade. A version number ending with a build identifier in the format `+build{yyyymmddhhmm}` indicates an [independent agent release version](./fleet-agent-release-process.md#independent-agent-releases).

In certain cases, the latest available {{agent}} version may not be recognized by {{kib}}. For instance, this occurs when the {{kib}} version is lower than the {{agent}} version. You can specify a custom version for {{agent}} to upgrade to by entering the version into the **Upgrade version** text field.

Expand Down
Loading