Add user-facing changelog entry for dynamic cpu changes #23227
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Pinging @elastic/integrations (Team:Integrations) |
botelastic
bot
added
needs_team
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. |
|
/test |
kaiyan-sheng
approved these changes
Dec 21, 2020
urso
approved these changes
Dec 23, 2020
|
Please backport the changelog update to each branch the original PR has been backported to. |
fearful-symmetry
added a commit
to fearful-symmetry/beats
that referenced
this pull request
Dec 28, 2020
(cherry picked from commit 86ad136)
1 task
fearful-symmetry
added a commit
that referenced
this pull request
Jan 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
#23154 Added a developer changelog entry, but this is technically a user-facing change as well, so we should have a changelog entry here.
Why is it important?
This needs to be documented in both the dev changelog and the user-facing changelog.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.