Elastic Agent release process
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Elastic Agent follows a release process aligned with the broader Elastic Stack release schedule. The latest features, enhancements, and fixes are documented in the release notes.
Independent Elastic Agent releases deliver critical fixes and updates for Elastic 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 Elastic Agent components needed for a targeted fix. For example, an independent Elastic 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.
In independent Elastic Agent releases, a build identifier is appended to the semantic version of the base release in the format +build{yyyymmddhhmm}, where {yyyymmddhhmm} is the release timestamp of the build.