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
In this particular situation, Elastic created a patch release for 8.15 after the last patch release for 8.16, which led to this downgrade.
Although these situations seem exceptional, we should not only validate that the release satisfies the semver, but also that it is greater than the current stack version.
Footnotes
with another 8.16 patch in between, but that's irrelevant for this issue. ↩
The text was updated successfully, but these errors were encountered:
antoineco
added
the
ci
Issues related to the automation pipeline: testing, updates, etc.
label
Dec 30, 2024
The update bot recently updated the stack from 8.15 to 8.16, then downgraded it to 8.15 again at a later time1:
This can happen because we pick the latest (GitHub) release by creation date that matches the major semver, then apply it blindly if it differs from the current stack version.
In this particular situation, Elastic created a patch release for 8.15 after the last patch release for 8.16, which led to this downgrade.
Although these situations seem exceptional, we should not only validate that the release satisfies the semver, but also that it is greater than the current stack version.
Footnotes
with another 8.16 patch in between, but that's irrelevant for this issue. ↩
The text was updated successfully, but these errors were encountered: