Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve elastic agent version handling #4578

Open
pchila opened this issue Apr 16, 2024 · 0 comments · May be fixed by #4573
Open

Improve elastic agent version handling #4578

pchila opened this issue Apr 16, 2024 · 0 comments · May be fixed by #4573
Labels
enhancement New feature or request

Comments

@pchila
Copy link
Contributor

pchila commented Apr 16, 2024

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).

@pchila pchila added the enhancement New feature or request label Apr 16, 2024
@pchila pchila linked a pull request Apr 16, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant