-
Notifications
You must be signed in to change notification settings - Fork 148
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
docs: add 8.8.0 changelog #2720
Conversation
- add missing fragments - fix changelog
🌐 Coverage report
|
changelog/8.8.0.yaml
Outdated
- kind: feature | ||
summary: Adds new StateWatch GRPC for watching the current state of the running Elastic Agent | ||
description: "" | ||
component: "" | ||
pr: | ||
- https://github.com/elastic/elastic-agent/pull/2252 | ||
issue: [] | ||
timestamp: 1676571093 | ||
file: | ||
name: 1676571093-control-state-watch.yaml | ||
checksum: 6f7a04fdd535f0c6de37545408e1d4dc4ffde6f7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to me, this change shouldn't be communicated to our users: it's not affecting them and will be use for our own purpose.
changelog/8.8.0.yaml
Outdated
summary: feature-flags | ||
description: | | ||
Add support for feature flags, starting with one to toggle FQDN reporting in | ||
events generated by Agent components, via the `host.name` field. | ||
component: agent | ||
pr: | ||
- https://github.com/elastic/elastic-agent/pull/2218 | ||
issue: | ||
- https://github.com/elastic/elastic-agent/issues/2185 | ||
timestamp: 1679422558 | ||
file: | ||
name: 1679422558-feature-flags.yaml | ||
checksum: f6a2c45b76df4b708f19d25ff569ab0394403eab |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
changelog/8.8.0.yaml
Outdated
- kind: feature | ||
summary: Allow users to specify custom base paths during installation | ||
description: "" | ||
component: agent | ||
pr: | ||
- https://github.com/elastic/elastic-agent/pull/2500 | ||
issue: [] | ||
timestamp: 1681940139 | ||
file: | ||
name: 1681940139-Allow-users-to-specify-custom-base-paths-during-installation.yaml | ||
checksum: 7f2cf8493a3d6cf61ff9f8117b965ff2ba327046 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It won't be officially released in 8.8.0 so we should remove it from the changelog.
changelog/8.8.0.yaml
Outdated
- kind: bug-fix | ||
summary: validate the --base-path value is an absolute path | ||
description: "" | ||
component: "" | ||
pr: | ||
- https://github.com/elastic/elastic-agent/pull/2567 | ||
issue: [] | ||
timestamp: 1684747237 | ||
file: | ||
name: 1684747237-validate---base-path-for-install-command.yaml | ||
checksum: e8f7ba2381f133ea505e968969550ca5ebada974 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix for an issue never released, we shouldn't mention it.
@AndersonQ I added some comments |
Don't forget to regenerate the asciidoc after you changed the yaml |
I've added a few small suggestions for the summaries in the yaml file. @pierrehilbert I had already put together the 8.8 release notes PR so I don't think this generated Asciidoc file needs editing, as it won't be used, but let me know if I'm mistaken about that. |
Correct, if you already added it, we can even remove it from this PR but we should ensure that the yaml file and the asciidoc in your PR are still aligned (because we never know ;-) ). |
changelog/8.8.0.yaml
Outdated
- kind: feature | ||
summary: Agent actions signature validation | ||
description: "" | ||
component: "" | ||
pr: | ||
- "2348" | ||
issue: [] | ||
timestamp: 1678136865 | ||
file: | ||
name: 1678136865-Agent-actions-signature-validation.yaml | ||
checksum: 372b3c9abff7d7723e032653d46234143ac647c6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this can be removed according to Craig's comment This was disabled in https://github.com/elastic/elastic-agent/commit/ce0542fd641ea3e13d29bb2f88ea0ec403d0eed0 without removing the changelog fragment.
Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
…t into 8.8-release-notes
Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> (cherry picked from commit 33df9fc) # Conflicts: # changelog/fragments/1684175757-bump-node-deps.yaml # changelog/fragments/1685029627-Fix-deadlock-condition-in-RuntimeManager.yaml
Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> (cherry picked from commit 33df9fc) # Conflicts: # changelog/fragments/1684175757-bump-node-deps.yaml # changelog/fragments/1685029627-Fix-deadlock-condition-in-RuntimeManager.yaml Co-authored-by: Anderson Queiroz <anderson.queiroz@elastic.co>
What does this PR do?
Add the 8.8.0 changelog
Why is it important?
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry in./changelog/fragments
using the changelog tool[ ] I have added an integration test or an E2E testRelated issues