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.2] [DOCS] Remove unneeded breaking changes pages (#36204) #36225

Closed
wants to merge 1 commit into from
Closed

[8.2] [DOCS] Remove unneeded breaking changes pages (#36204) #36225

wants to merge 1 commit into from

Conversation

jrodewig
Copy link
Contributor

@jrodewig jrodewig commented Aug 3, 2023

Backport

This will backport the following commits from main to 8.2:

Questions ?

Please refer to the Backport tool documentation

Removes several unneeded breaking changes pages (Ex: [8.4](https://www.elastic.co/guide/en/beats/libbeat/current/breaking-changes-8.4.html)) from the Beats Platform reference.

Beats hasn't released a breaking change since 8.0. These pages just add additional admin/docs overhead. They haven't been updated since 8.5.

(cherry picked from commit 78fc965)

# Conflicts:
#	libbeat/docs/release-notes/breaking/breaking.asciidoc
@jrodewig jrodewig requested a review from a team as a code owner August 3, 2023 13:49
@jrodewig jrodewig requested review from ycombinator and leehinman and removed request for a team August 3, 2023 13:49
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Aug 3, 2023
@botelastic
Copy link

botelastic bot commented Aug 3, 2023

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-08-03T13:50:11.516+0000

  • Duration: 24 min 57 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@jrodewig jrodewig closed this Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants