You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elastic Agent uses a semver-like versioning scheme like <major>.<minor>.<patch>[-<prerelease>][+<build metadata>].
At the time of writing, the prerelease is used to identify SNAPSHOT version and the build metadata part is used for repackaging agent in the context of prereleases.
The handling of version though works only for snapshots OR early releases: trying to create an early release from SNAPSHOT or trying to cram further prerelease tokens in a given version leads to some funny results (non-compliant with semver format).
The goal of this issue to fix elastic agent version handling during packaging and runtime so that a generic version string can be correctly handled (for example 8.14.0-SNAPSHOT.repackaged+build20240416122259).
The text was updated successfully, but these errors were encountered:
Elastic Agent uses a semver-like versioning scheme like
<major>.<minor>.<patch>[-<prerelease>][+<build metadata>]
.At the time of writing, the
prerelease
is used to identify SNAPSHOT version and thebuild metadata
part is used for repackaging agent in the context of prereleases.The handling of version though works only for snapshots OR early releases: trying to create an early release from SNAPSHOT or trying to cram further prerelease tokens in a given version leads to some funny results (non-compliant with semver format).
The goal of this issue to fix elastic agent version handling during packaging and runtime so that a generic version string can be correctly handled (for example
8.14.0-SNAPSHOT.repackaged+build20240416122259
).The text was updated successfully, but these errors were encountered: