Skip to content

The Gazette: weekly release-note harvest - #566

Closed
github-actions[bot] wants to merge 18 commits into
mainfrom
gazette/weekly-release-note-harvest
Closed

The Gazette: weekly release-note harvest#566
github-actions[bot] wants to merge 18 commits into
mainfrom
gazette/weekly-release-note-harvest

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

The Gazette compiled release-note partials into a draft release notes page.

Generated file:

  • docs/modules/release-notes/pages/all-releases/gazette-preview.adoc

This PR was generated from release-note partials under:

  • docs/modules/release-notes/partials/

Review notes:

  • Confirm included entries are assigned to the correct release.
  • Rename or move the generated page if publishing for a specific release date.
  • Confirm nav/sidebar placement if this page should be published.
  • Product-doc changes bundled in source PRs are not applied here.

tiffany-kobiton and others added 6 commits August 14, 2026 15:43
First collection doc for date-based CI/CD release notes post-4.28.
Aggregates entries from PRs #540, #541, #548, #549 and KOB-48664
(sourced from Slack; no Robot Ranch PR was generated).

Structural decisions (filename, title, per-release-date sectioning,
new-features vs improvements-and-fixes classification) are placeholders
and flagged inline for reviewer input. Product doc updates bundled in
PRs #548 and #549 are held for a separate pass and remain parked on
their source PRs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Original text:

// KOB-51470 (PR #539): fix was in open PRs and had not completed test validation when the draft
// was written. Standalone-only change — no post-4.28 Standalone release page exists yet, so
// filing under the collection doc with a Standalone callout in the entry text.

== Security Banner

- Fixed *Settings > Security Banner* being blocked on Standalone deployments. The page displayed _Security Banner setting page is available by upgrading your plan_ instead of the banner editor, which prevented admins from editing or publishing the login message and stopped published banners from appearing to users at sign-in.
+
** Subscription expiry no longer gates the Security Banner on Standalone deployments, where plan upgrades do not apply. Cloud deployments are unaffected.
** Permission requirements are unchanged. Only *Admins* or users with the `org_setting.modify_security_banner` permission can change the xref:organization:change-the-login-message.adoc[login message,window=read-later].
@tiffany-kobiton tiffany-kobiton added the new doc An entirely new page must be made label Aug 20, 2026
tiffany-kobiton and others added 3 commits August 25, 2026 11:39
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@tiffany-kobiton

Copy link
Copy Markdown
Contributor

Merged my manual PR 555 to this branch.
Added blurb describing new versioning pattern.
Checked on all candidate review tickets and confirmed none were needed as they had already been addressed and are still waiting for review and merge.
Ending pattern added.

Added KOB-54483 info.
Why it was "missing": Ticket didn't go through the standard EPB/spec-folder flow — it was filed directly as a bug against XIUM by QA and fixed quickly. No spec folder in .ai, no docs-writer trigger, so The Gazette had nothing to harvest.

@tiffany-kobiton

tiffany-kobiton commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

NOTE: This collection of release notes is Cloud ONLY. Phoenix team releases are not documented here and are not part of The Gazette process. The Gazette only collects documentation PRs made in this repo by Portal team's Robot Ranch workflow.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@tiffany-kobiton

Copy link
Copy Markdown
Contributor

Superseded by #570 — attribution errors corrected there. Closing as obsolete.

tiffany-kobiton added a commit that referenced this pull request Sep 3, 2026
## Summary

Six weeks of release notes across DLM Team (Portal) and Phoenix Team
(deviceConnect / Gigacap) compiled into per-week `.adoc` pages under
`docs/modules/release-notes/pages/all-releases/`. Two Standalone pages
added for weeks that shipped Standalone-only fixes. `nav.adoc` updated
at the top of the All-releases list.

**Pages added:**

| Week | Cloud | Standalone |
| --- | --- | --- |
| Jul 24 | `2026-07-24.adoc` | — |
| Jul 31 | `2026-07-31.adoc` | `2026-07-31-standalone.adoc` (KOB-54281
CLI install) |
| Aug 7 | `2026-08-07.adoc` | — |
| Aug 14 | `2026-08-14.adoc` | — |
| Aug 21 | `2026-08-21.adoc` | `2026-08-21-standalone.adoc` (KOB-54549
Kibana on Updater) |
| Aug 28 | `2026-08-28.adoc` | — |

## Compilation methodology

- **Roster source:** Jira project KOB, `status in ("Released",
"Deployed") AND resolutiondate >= 2026-07-18 AND resolutiondate <=
2026-08-28`, plus a supplementary changelog-verified query for tickets
without `resolutiondate`.
- **Filters applied at roster time:** user-facing only (internal /
testing / infra / routine MCP-tool tweaks dropped up front); `AYA`
component excluded entirely (unreleased); `virtualUSB` preserved but
wrapped in `////` block comments (unreleased-but-in-progress).
- **PR #566 reuse:** already-drafted entries are reused verbatim on the
correct weekly pages (KOB-48664 → Aug 14, KOB-53798 → Aug 7, KOB-54289 →
Aug 7 restored, KOB-54483 → Aug 14, KOB-53962 → Aug 21). PR #566 stays
open for reference; this PR does not replace it.

## Reviewer aids

Every entry has a hidden `// REVIEWER NOTE:` block with `KOB-ID | Team |
Deployment | ship_date | bucket_source`. Every entry whose bucket relies
on the `updated`-date fallback also carries `// bucket:updated — verify`
so misplaced entries can be moved during review. `TODO:` markers on
`Component versions` blocks and any thin descriptions.

## Findings worth reviewer attention

- **PR #566 section-attribution errors** — reviewer-note KOB IDs in PR
#566 are shifted by one section throughout the file. Corrected mappings
noted on each affected new page (Aug 7, Aug 14, Aug 21, Jul 31).
- **Compilation drops** — each page's file-top comment lists the tickets
that were in the initial roster but dropped for that week (OOW
fixVersion or internal). Two tickets moved between weeks: KOB-54428 (Aug
7 → Aug 14, fixVersion 2026.08.15), KOB-43481 (Aug 21 → Jul 31,
fixVersion 2026.07.29).
- **Aug 28 bucket inflation** — 24 of 32 remaining entries rely on
`updated`-fallback bucketing. Today's (2026-08-27) mass component-edit
in Jira touched many tickets and moved their `updated` timestamps to
today. Verify each Aug 28 entry actually shipped in the Aug 24-28 window
before publishing.
- **"Released" is a soft signal for DLM** — per the DLM lead, some DLM
tickets marked "Released" are gated by incomplete parent features and
are not yet user-visible. Confirm anything suspicious before publishing.
- **Component versions** — most weeks lack ticket-level `fixVersion`
coverage. `TODO:` markers left for the release team to fill in Portal /
deviceConnect / bluetoothBridge / Gigacap versions per week.

## Test plan

- [ ] Preview each page in Antora locally and confirm the `Cloud <Month>
<Day>, 2026` heading + date-versioning NOTE block render.
- [ ] Verify `nav.adoc` places all eight new pages at the top of the
*All releases* list.
- [ ] Confirm `////` block comments hide the virtualUSB sections from
the rendered output.
- [ ] Spot-check three or four `bucket:updated — verify` entries against
their Jira changelog to catch any misplaced entries.
- [ ] Fill in the `Component versions` blocks per the release-team's
version tracking.
- [ ] Reconcile PR #566: either close in favor of this PR, merge PR #566
first and reconcile drift here, or apply the section-attribution
corrections back to PR #566.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new doc An entirely new page must be made ready for review Doc is ready for review release note Release note level updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant