Bumps current to 8.15.0 #3036
Merged
Bumps current to 8.15.0 #3036
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
|
A documentation preview will be available soon. Request a new doc build by commenting
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. |
1 task
|
run docs-build rebuild |
This comment was marked as outdated.
This comment was marked as outdated.
|
I'm a dummy. elastic/kibana#190061 hasn't been merged yet. |
This is expected because elastic/kibana#190061 isn't merged yet. I'll rerun the build here again after it merges! |
colleenmcginnis
added a commit
to elastic/kibana
that referenced
this pull request
Aug 7, 2024
## Summary In #179981 we moved the APM UI content to the Observability guide. When [backporting to the `8.14` branch](#190009) (which is the `current` branch at the time I'm writing this) the docs build failed because there are some links in the APM agent docs that are hard-coded to go to the `current` version of the docs, and those links were not properly redirected. When [`8.15` becomes the `current` branch](elastic/docs#3036), I believe the docs build will fail unless we implement the AsciiDoc redirects in this PR. ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Aug 7, 2024
…190061) ## Summary In elastic#179981 we moved the APM UI content to the Observability guide. When [backporting to the `8.14` branch](elastic#190009) (which is the `current` branch at the time I'm writing this) the docs build failed because there are some links in the APM agent docs that are hard-coded to go to the `current` version of the docs, and those links were not properly redirected. When [`8.15` becomes the `current` branch](elastic/docs#3036), I believe the docs build will fail unless we implement the AsciiDoc redirects in this PR. ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) (cherry picked from commit 5bce919)
kibanamachine
added a commit
to elastic/kibana
that referenced
this pull request
Aug 7, 2024
…190061) (#190085) # Backport This will backport the following commits from `main` to `8.15`: - [[DOCS] Add more APM UI redirects to the Observability guide (#190061)](#190061) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Colleen McGinnis","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-08-07T16:42:45Z","message":"[DOCS] Add more APM UI redirects to the Observability guide (#190061)\n\n## Summary\r\n\r\nIn #179981 we moved the APM UI\r\ncontent to the Observability guide. When [backporting to the `8.14`\r\nbranch](#190009) (which is the\r\n`current` branch at the time I'm writing this) the docs build failed\r\nbecause there are some links in the APM agent docs that are hard-coded\r\nto go to the `current` version of the docs, and those links were not\r\nproperly redirected. When [`8.15` becomes the `current`\r\nbranch](elastic/docs#3036), I believe the docs\r\nbuild will fail unless we implement the AsciiDoc redirects in this PR.\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5bce919cf11c618057093940157ca35e95fc4eb0","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.15.0","v8.16.0"],"title":"[DOCS] Add more APM UI redirects to the Observability guide","number":190061,"url":"https://github.com/elastic/kibana/pull/190061","mergeCommit":{"message":"[DOCS] Add more APM UI redirects to the Observability guide (#190061)\n\n## Summary\r\n\r\nIn #179981 we moved the APM UI\r\ncontent to the Observability guide. When [backporting to the `8.14`\r\nbranch](#190009) (which is the\r\n`current` branch at the time I'm writing this) the docs build failed\r\nbecause there are some links in the APM agent docs that are hard-coded\r\nto go to the `current` version of the docs, and those links were not\r\nproperly redirected. When [`8.15` becomes the `current`\r\nbranch](elastic/docs#3036), I believe the docs\r\nbuild will fail unless we implement the AsciiDoc redirects in this PR.\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5bce919cf11c618057093940157ca35e95fc4eb0"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/190061","number":190061,"mergeCommit":{"message":"[DOCS] Add more APM UI redirects to the Observability guide (#190061)\n\n## Summary\r\n\r\nIn #179981 we moved the APM UI\r\ncontent to the Observability guide. When [backporting to the `8.14`\r\nbranch](#190009) (which is the\r\n`current` branch at the time I'm writing this) the docs build failed\r\nbecause there are some links in the APM agent docs that are hard-coded\r\nto go to the `current` version of the docs, and those links were not\r\nproperly redirected. When [`8.15` becomes the `current`\r\nbranch](elastic/docs#3036), I believe the docs\r\nbuild will fail unless we implement the AsciiDoc redirects in this PR.\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"5bce919cf11c618057093940157ca35e95fc4eb0"}}]}] BACKPORT--> Co-authored-by: Colleen McGinnis <[email protected]>
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.
Do not merge until release day