[DOCS] Fix bundle release lifecycle and release dates#280898
Conversation
|
Pinging @elastic/experience-docs (Team:Docs) |
🔍 Preview links for changed docs⏳ Building and deploying preview... View progress This comment will be updated with preview links when the build is complete. |
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
There was a problem hiding this comment.
One typo in a release date; the rest of the bundle lifecycle and date updates look consistent.
Generated by Claude Reviewer for #280898 · 7.92 AIC · ⌖ 0.98 AIC
| lifecycle: ga | ||
| repo: kibana | ||
| owner: elastic | ||
| release-date: 2026-06-16w |
There was a problem hiding this comment.
The release date has a stray trailing w, so this bundle records an invalid date (2026-06-16w) unlike every other file in this PR. This will render an incorrect release date or break date parsing in docs-builder.
| release-date: 2026-06-16w | |
| release-date: 2026-06-16 |
💚 Build Succeeded
|
Summary
Relates to elastic/docs-builder#3725, elastic/docs-builder#3700
This PR:
lifecycle: gainstead ofpreviewbundle.resolvefrom the changelog configuration filebundle.branchto the changelog configuration fileChecklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support- [ ] Documentation was added for features that require explanation or tutorials- [ ] Unit or functional tests were updated or added to match the most common scenarios- [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list- [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. Therelease_note:breakinglabel should be applied in these situations.- [ ] Flaky Test Runner was used on any tests changed- [ ] The PR description includes the appropriate Release Notes section, and the correctrelease_note:*label is applied per the guidelinesbackport:*labels.Identify risks
N/A