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

[8.16] [main](backport #1349) Clarification of MSI Upgrading Behavior (backport #1440) #1442

Merged
merged 1 commit into from
Nov 6, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 6, 2024

Rephrased to clarify that upgrades via fleet are supported, but the impact is that the MSI version remains registered at the initially installed package version. Added suggestion for MSI installs (package management) that in order to upgrade an uninstall/reinstall is required.


This is an automatic backport of pull request #1349 done by Mergify.
This is an automatic backport of pull request #1440 done by Mergify.

Co-authored-by: David Kilfoyle <[email protected]>
(cherry picked from commit 277e29d)

Co-authored-by: Thomas Youngs <[email protected]>
(cherry picked from commit 76ffa45)
@mergify mergify bot requested a review from a team as a code owner November 6, 2024 14:46
@mergify mergify bot added the backport label Nov 6, 2024
Copy link

github-actions bot commented Nov 6, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@kilfoyle kilfoyle merged commit 6ed639a into 8.16 Nov 6, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant