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

[Fleet] Remove agent upgrade fix from 8.11.1 release notes #171200

Merged
merged 1 commit into from
Nov 14, 2023

Conversation

kpollich
Copy link
Member

@kpollich kpollich commented Nov 14, 2023

Summary

The 8.11.1 release notes included #170974 which didn't actually land in 8.11.1. We shipped BC2 of 8.11.1 which was built from this Kibana commit: https://github.com/elastic/kibana/commits/09feaf416f986b239b8e8ad95ecdda0f9d56ebec. The PR was not merged until after this commit, so the bug is still present (though mitigated slightly) in 8.11.1.

This PR removes the erroneous release note from the 8.11.1 release notes. How can we make sure the fix does get included in the eventual 8.11.2 release notes?

@kpollich kpollich added Team:Docs release_note:skip Skip the PR/issue when compiling release notes labels Nov 14, 2023
@kpollich kpollich self-assigned this Nov 14, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-docs (Team:Docs)

Copy link
Contributor

Documentation preview:

@apmmachine
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • /oblt-deploy-serverless : Deploy a serverless Kibana instance using the Observability test environments.
  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@kilfoyle kilfoyle added auto-backport Deprecated - use backport:version if exact versions are needed v8.11.2 labels Nov 14, 2023
Copy link
Contributor

@kilfoyle kilfoyle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! ⛵

@kilfoyle
Copy link
Contributor

@amyjtechwriter We'd like this to backport into the 8.11 branch so I added v8.11.2 and auto-backport labels. However, I noticed that the description for the auto-backport label says that it's deprecated. Is there a different way that we should backport this PR?

@kpollich kpollich added backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) and removed auto-backport Deprecated - use backport:version if exact versions are needed labels Nov 14, 2023
@kpollich
Copy link
Member Author

@kilfoyle - The newer way to backport is the backport:prev-minor label which doesn't require a specific version to work. I've updated the labels here.

@amyjtechwriter
Copy link
Contributor

@kpollich I'm happy to manually make sure it's included in 8.11.2

@kilfoyle
Copy link
Contributor

@amyjtechwriter Thanks for making sure the change will be included in 8.11.2. Is it okay for us to merge this PR?

@amyjtechwriter
Copy link
Contributor

@kilfoyle and @kpollich Yes please merge away!

@kilfoyle kilfoyle merged commit 480fcef into elastic:main Nov 14, 2023
18 checks passed
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Nov 14, 2023
…71200)

## Summary

The 8.11.1 release notes included elastic#170974 which didn't actually land in
8.11.1. We shipped BC2 of 8.11.1 which was built from this Kibana
commit:
https://github.com/elastic/kibana/commits/09feaf416f986b239b8e8ad95ecdda0f9d56ebec.
The PR was not merged until after this commit, so the bug is still
present (though [mitigated
slightly](elastic#169825 (comment)))
in 8.11.1.

This PR removes the erroneous release note from the 8.11.1 release
notes. How can we make sure the fix _does_ get included in the eventual
8.11.2 release notes?

(cherry picked from commit 480fcef)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.11

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Nov 14, 2023
…71200) (#171249)

# Backport

This will backport the following commits from `main` to `8.11`:
- [[Fleet] Remove agent upgrade fix from 8.11.1 release notes
(#171200)](#171200)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Kyle
Pollich","email":"kyle.pollich@elastic.co"},"sourceCommit":{"committedDate":"2023-11-14T21:57:06Z","message":"[Fleet]
Remove agent upgrade fix from 8.11.1 release notes (#171200)\n\n##
Summary\r\n\r\nThe 8.11.1 release notes included #170974 which didn't
actually land in\r\n8.11.1. We shipped BC2 of 8.11.1 which was built
from this
Kibana\r\ncommit:\r\nhttps://github.com/elastic/kibana/commits/09feaf416f986b239b8e8ad95ecdda0f9d56ebec.\r\nThe
PR was not merged until after this commit, so the bug is
still\r\npresent (though
[mitigated\r\nslightly](https://github.com/elastic/kibana/issues/169825#issuecomment-1808453016))\r\nin
8.11.1.\r\n\r\nThis PR removes the erroneous release note from the
8.11.1 release\r\nnotes. How can we make sure the fix _does_ get
included in the eventual\r\n8.11.2 release
notes?","sha":"480fcef6985b21c1a3c22d4657aeefc761fec5a3","branchLabelMapping":{"^v8.12.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport:prev-minor","v8.12.0","v8.11.2"],"number":171200,"url":"https://github.com/elastic/kibana/pull/171200","mergeCommit":{"message":"[Fleet]
Remove agent upgrade fix from 8.11.1 release notes (#171200)\n\n##
Summary\r\n\r\nThe 8.11.1 release notes included #170974 which didn't
actually land in\r\n8.11.1. We shipped BC2 of 8.11.1 which was built
from this
Kibana\r\ncommit:\r\nhttps://github.com/elastic/kibana/commits/09feaf416f986b239b8e8ad95ecdda0f9d56ebec.\r\nThe
PR was not merged until after this commit, so the bug is
still\r\npresent (though
[mitigated\r\nslightly](https://github.com/elastic/kibana/issues/169825#issuecomment-1808453016))\r\nin
8.11.1.\r\n\r\nThis PR removes the erroneous release note from the
8.11.1 release\r\nnotes. How can we make sure the fix _does_ get
included in the eventual\r\n8.11.2 release
notes?","sha":"480fcef6985b21c1a3c22d4657aeefc761fec5a3"}},"sourceBranch":"main","suggestedTargetBranches":["8.11"],"targetPullRequestStates":[{"branch":"main","label":"v8.12.0","labelRegex":"^v8.12.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/171200","number":171200,"mergeCommit":{"message":"[Fleet]
Remove agent upgrade fix from 8.11.1 release notes (#171200)\n\n##
Summary\r\n\r\nThe 8.11.1 release notes included #170974 which didn't
actually land in\r\n8.11.1. We shipped BC2 of 8.11.1 which was built
from this
Kibana\r\ncommit:\r\nhttps://github.com/elastic/kibana/commits/09feaf416f986b239b8e8ad95ecdda0f9d56ebec.\r\nThe
PR was not merged until after this commit, so the bug is
still\r\npresent (though
[mitigated\r\nslightly](https://github.com/elastic/kibana/issues/169825#issuecomment-1808453016))\r\nin
8.11.1.\r\n\r\nThis PR removes the erroneous release note from the
8.11.1 release\r\nnotes. How can we make sure the fix _does_ get
included in the eventual\r\n8.11.2 release
notes?","sha":"480fcef6985b21c1a3c22d4657aeefc761fec5a3"}},{"branch":"8.11","label":"v8.11.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co>
@amyjtechwriter amyjtechwriter mentioned this pull request Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) release_note:skip Skip the PR/issue when compiling release notes Team:Docs v8.11.2 v8.12.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants