Skip to content

Catch-up release notes: weekly pages for Jul 24 - Aug 28, 2026 - #570

Open
tiffany-kobiton wants to merge 21 commits into
mainfrom
docs/catch-up-release-notes-jul24-aug28
Open

Catch-up release notes: weekly pages for Jul 24 - Aug 28, 2026#570
tiffany-kobiton wants to merge 21 commits into
mainfrom
docs/catch-up-release-notes-jul24-aug28

Conversation

@tiffany-kobiton

Copy link
Copy Markdown
Contributor

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 The Gazette: weekly release-note harvest #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 The Gazette: weekly release-note harvest #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 The Gazette: weekly release-note harvest #566 section-attribution errors — reviewer-note KOB IDs in PR The Gazette: weekly release-note harvest #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 The Gazette: weekly release-note harvest #566: either close in favor of this PR, merge PR The Gazette: weekly release-note harvest #566 first and reconcile drift here, or apply the section-attribution corrections back to PR The Gazette: weekly release-note harvest #566.

🤖 Generated with Claude Code

Compile six weeks of release notes across the DLM Team (Portal) and
Phoenix Team (deviceConnect / Gigacap) release streams into per-week
pages under all-releases/, plus two Standalone pages for weeks that
shipped Standalone changes.

Source of truth is Jira project KOB. Roster was built from a
resolutiondate-based JQL query plus a changelog-verified supplementary
query for tickets without resolutiondate. User-facing filter applied
(internal / testing / infra / routine MCP-tool tweaks dropped at roster
time, not during drafting). AYA tickets excluded entirely per the
"unreleased" component convention. virtualUSB entries are preserved as
`////` block comments so they are held for future release.

Every entry carries a hidden reviewer note with `KOB-ID | Team |
Deployment | ship_date | bucket_source`. Entries bucketed via the
`updated`-date fallback (108 of ~156) also carry a
`// bucket:updated — verify` flag so reviewers can move any misplaced
entries during review.

PR #566 remains open for reference. This PR reuses its already-drafted
entries verbatim where they belong (KOB-48664 on Aug 14, KOB-53798 and
KOB-54289 on Aug 7, KOB-54483 on Aug 14, KOB-53962 on Aug 21) and
corrects PR #566's shifted section-attribution reviewer notes inline.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Removed section about public documentation updates including site search and AI assistant.
Removed notes related to ticket verification and PR attribution for clarity.
Removed outdated reviewer notes and clarified attribution for changes in the device modal and accessibility fixes.
Standalone releases are ad-hoc and not on the Cloud weekly Friday
cadence — the release team is finalizing the Updater before deciding
whether Standalone shifts to a regular cycle. A Standalone-tagged
ticket marked "Released" in Jira has not necessarily shipped to
Standalone customers.

Delete the two weekly Standalone pages and their nav entries.
Move the two deferred tickets (KOB-54281 CLI install, KOB-54549
Kibana on Updater) into `// Standalone deferred` reviewer comments
at the top of the Jul 31 and Aug 21 Cloud pages so they're not lost.

Per the release team's convention, the next Standalone release note
will be comprehensive — bundling these queued Standalone-specific
items together with the relevant Cloud items customers running
Standalone need to know about — rather than a Standalone-tagged
subset of the weekly Cloud stream.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Scanned all 130+ shipped tickets across the six weekly rosters for
`dl.kobiton.download` / `public.kobiton.download` URLs in Jira
comments. 17 tickets have URLs; most trace back to a mass bulk-status
comment posted across the shipped-and-deployed set.

Extracted component versions per the YYMM.DD rule (first two dotted
segments of the build number):

- 2026-08-07: deviceConnect 2608.7, Kobiton CLI 2608.7
- 2026-08-14: deviceConnect 2608.12, Kobiton CLI 2608.11, gigacap 2608.12
- 2026-08-21: deviceConnect 2608.20, Kobiton CLI 2608.19
- 2026-08-28: deviceConnect 2608.26, gigacap 2608.25

Portal has no build URL in the ticket-comment stream (it's distributed
differently). Portal TODOs remain on every page for the release team
to fill in. Kobiton CLI on Aug 28 also has no matching URL — TODO.

The Jul 24 and Jul 31 pages have no build URLs at all. The mass
bulk-status comment convention appears to have started with the Aug 7
wave, so those two pages carry an explanatory TODO instead.

Each populated block also carries the extraction source in comments so
a reviewer can trace back to the specific URL if a version needs
verification.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Remove the commented-out virtualUSB blocks from the 2026-07-24, 2026-08-14,
and 2026-08-28 pages, and drop the passing "+ virtualUSB" note from the
2026-08-14 dropped-tickets reviewer comment.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Comment thread docs/modules/release-notes/pages/all-releases/2026-08-28.adoc Outdated
Comment thread docs/modules/release-notes/pages/all-releases/2026-08-28.adoc
Removed draft comments and clarified Bluetooth Keyboard support details.
Comment thread docs/modules/release-notes/pages/all-releases/2026-08-21.adoc Outdated
Comment thread docs/modules/release-notes/pages/all-releases/2026-08-21.adoc
Removed outdated comments and clarified fix version in release notes.
Comment thread docs/modules/release-notes/pages/all-releases/2026-08-14.adoc
Comment thread docs/modules/release-notes/pages/all-releases/2026-08-14.adoc Outdated
Comment thread docs/modules/release-notes/pages/all-releases/2026-08-07.adoc
Comment thread docs/modules/release-notes/pages/all-releases/2026-07-31.adoc Outdated
The prior bullet had the direction of the change reversed. Per the
Jira description ("Add built-in retries to all resource connections
in case connection failures are transient" + "Broaden file pull
transient error detection to cover some tonic errors"), retries were
*added* for transient failures, not limited.

Rewrote the two bullets to reflect the actual change and updated the
reviewer block:

- bucket_source corrected to updated_fallback (not changelog)
- PLACEMENT NOTE flags fixVersion `2026 Q2 - 4.27` (shipped 4.28 on
  Jul 17) — this entry belongs on the 4.28 page but was not
  documented there. Landing on 2026-07-24 so the change is captured
  somewhere; do not retroactively edit 4.28.
- TODO carries the unverified "~600ms retry window" figure and points
  at Chris Faulhaber for confirmation before publish.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
KOB-54047 (per-skill environment rules):
- Renamed heading from "Portal auto-plugin enforcement" to
  "Kobiton MCP server: per-skill environment rules". The prior
  heading used the internal repo name ("automate") and misattributed
  the change to Portal. Users know this surface as the Kobiton MCP
  server.
- Added a second bullet giving context on why the enforcement
  matters (the MCP server runs across hosts with different
  capabilities — Claude Chat, Claude Code, Gemini, Codex, Cursor,
  Copilot CLI — so preconditions like local file access or macOS
  now surface up front instead of failing opaquely).
- Dropped the "expand from ticket description" TODO.

KOB-43481 (Test Step labels during Revisit):
- Expanded "new action name" to describe both states: at conversion
  time steps display human-friendly labels (`Tap`, `Press Back`,
  `Install`); during Revisit they switch to the forward-slash-
  prefixed Appium endpoint (`/click`, `/back`, `/orientation`),
  which matches how the step is referenced in the automation
  script.
- Dropped the "confirm the exact format" TODO.

Component versions block left as-is with its explanatory TODO —
Portal 2607.29 is the only version derivable for this bucket; the
build-URL comment convention hadn't started yet.

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

KOB-53798 (mixed-session convert + Revisit):
- Renamed section from "Convert a mixed session into a Test Case" to
  "Convert a combined manual + automation session into a Test Case".
  "Mixed session" isn't a natural user-facing framing; underlying
  UI tokens users actually see (`Mixed` Source type on the Test
  Cases list, `type:mixed` search keyword) are preserved verbatim.
- Reworded bullets to consistently reference "manual and automation
  steps" instead of the "mixed" concept name.
- Reviewer note updated to record that placement was confirmed
  during refinement (Released + Deployed) and to log the wording
  rationale.

KOB-52004 (VoiceOver / TalkBack audio):
- Stripped implementation detail from the user-facing bullet. The
  prior bullet described WebRTC API migration, muted-start-then-
  unmute mechanics, and browser autoplay policy — none of which is
  what the customer observes. Replaced with a single bullet
  describing the observable change: screen readers now play audio
  immediately at session start and immediately after an app
  install, on iOS and Android.
- Dropped the second bullet about the `?webrtcDebugPanelEnabled=true`
  debug panel — that's engineering diagnostics, not a customer
  feature.
- Preserved implementation detail in the reviewer note so context
  isn't lost internally.

KOB-54439 (deviceConnect Console sign-in):
- Removed the section entirely. The engineer's own ticket comments
  suggest an environment issue rather than a code fix (intermittent,
  inconsistent responses, only reproduces when `dc.ini` points at
  test, specific host IP called out). deviceConnect Console is a
  Standalone surface, so the entry doesn't belong on a Cloud page
  even if the fix were real. Drop reasoning added to the file-top
  comment for Tung's visibility when Standalone notes are written.
- Removed the corresponding "confirm device Connect Console version"
  TODO from the Component versions block.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…OB-54468+KOB-54472)

KOB-52121 (Appium find element with LLM vision / visionvirtual):
- Removed the section entirely. This feature was already documented
  in 4.26S as "Appium AI: Natural language locators (Beta)"; the
  updated_fallback bucketing landed it here on the Aug 11 update
  timestamp, but the feature shipped in 4.26S. Drop reasoning added
  to the top-of-file comment.

KOB-54550 (Kobiton MCP server: run-interactive-session platform support):
- Rewrote from a five-bullet plumbing-heavy entry to one bullet
  describing what the customer gains: the `run-interactive-session`
  skill now runs on Windows (x64) and Linux (x64) in addition to
  macOS; Apple Silicon uses the native build (no Rosetta 2).
- Renamed section from "Kobiton CLI — Windows and Linux support,
  unbundled binary" to "Kobiton MCP server: run-interactive-session
  on Windows and Linux". The prior heading was misleading — the
  Kobiton CLI itself already supported those platforms; what's new
  is the MCP plugin's skill.
- Dropped internal detail from the user-facing entry: binary
  unbundling, checksum verification, cache path, install-script
  mechanics, Claude Code SessionStart hook plumbing, `/automate:doctor`
  drift check, and the "never defaults to `latest`" pin policy. All
  captured in the reviewer note for future context.

KOB-54468 + KOB-54472 (Restricted ADB shell):
- Dropped "deny-by-default whitelist" framing — internal
  implementation the customer doesn't see directly.
- Dropped the historical "PUT was previously blocked / GET was
  previously unchecked" bullet and the internal path-validation
  mechanics (control chars, metacharacters, `..` traversal,
  safe-directory prefixes).
- Reworked the scope clause from "public cloud and trial devices"
  to "Public Devices" (title case matches UI label; no meaningful
  user-facing distinction between public and trial) and from
  "Unrestricted (private cloud / dedicated) devices are unaffected"
  to "Private Devices are unaffected" (matches UI label; existing
  product docs treat "dedicated" as a modifier on Private / Standalone
  devices, not a separate tier).

KOB-54428 (Kobiton CLI booking placement TODO):
- Dropped the "if the fix went live before Aug 10, move to Aug 7"
  TODO. fixVersion 2026.08.15 places it in the Aug 10-16 window;
  Aug 14 is correct.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
tiffany-kobiton and others added 3 commits August 31, 2026 13:47
Reviewer notes should carry durable ticket facts, not cross-branch
compilation-history references.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Two spots on the page referenced a parallel compilation PR — the
KOB-54483 reviewer note and the Component versions Portal-build
TODO. Reviewer notes should carry durable ticket facts, not
cross-branch compilation-history references.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Kobiton version management (renamed to "deviceConnect version display
and upgrade banner"):
- Rewrote three bullets to describe what the customer observes: new
  date-based version strings render correctly in Device Management,
  a new informational banner appears for Org Admins with the exact
  copy from KOB-54286's acceptance criteria, and machines previously
  forced offline come back online automatically.
- Dropped EPA-01/EPA-02/EPA-04 internal codes, R2/Nexus distribution
  names, "non-punitive" engineering framing, and the self-referential
  "parent epic wraps up" project-management language.

API v2 — Terminate reservation by device UDIDs (KOB-54045):
- Expanded from "POST to the terminate-reservation endpoint" to the
  actual method + path (`DELETE /v2/reservations/terminate`) with the
  parameter (`reservation_ids` + UDIDs), the `failed` list behavior
  for UDIDs with no active reservation, backward-compat note, and
  the unchanged authorization filter.

Kobiton CLI (KOB-54547):
- Expanded "New: create a user via the Kobiton CLI" to the full
  command syntax (`kobiton org user create`), required and optional
  flags, the `--password` / `--enable-sso` mutual exclusion, the
  `KOBITON_NEW_USER_PASSWORD` env-var alternative for keeping the
  password out of shell history, and the required
  `org_management.modify` role permission.

KOB-44438 (gRPC upstreaming deprecation):
- Removed the section entirely. Per the ticket description, this was
  dead-code cleanup ("we no longer have ever desire to upstream video
  via gRPC. Thus the code that supports this is now dead code in dC
  and should be removed for simplification."). Nothing in production
  relied on it; the prior draft incorrectly framed it as a customer-
  facing deprecation. Drop rationale added to the top-of-file
  backend-only list.

Device Hub (KOB-54584):
- Rewrote to lead with the customer-visible symptom: devices getting
  stuck as unavailable (`MH-400 ... is being used for CLI testing`)
  after abnormal CLI session ends. Internal mechanics (`getErrorMessage`
  crash, stream-end fallback, TTL) moved to the reviewer note.

deviceConnect fixes:
- Rewrote KOB-54640 (WatchDog service recovery) to describe the
  observable failure — internal services on macOS host machines
  couldn't be restarted automatically after a failure timeout —
  without naming WatchDog, `runit sv`, or the launchd migration.
- Dropped KOB-54639 (InstrumentsClient NRE + leak) entirely. Per
  the ticket: "8 leaks over ~19h will not exhaust resources on its
  own — this is a broken-teardown marker, not a resource-exhaustion
  cause. It has not been shown to cause the watchdog restarts on
  that host." No proven customer symptom; internal hygiene. Added
  to the top-of-file backend-only list.
- Simplified the `adb shell reboot bootloader` bullet from "rejected
  under the restricted whitelist" to "The command is now rejected."
  Same "whitelist" leak the Aug 14 restricted-ADB-shell rewrite
  already addressed.

Also dropped one source-PR reference from the KOB-53962 reviewer
note.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ium AI, small cleanups

Duplicate content dropped:
- KOB-53041/42/43/44/45 (Portal auto-logout, EPA 1-5) — already
  documented in 4.28 release notes as "Portal Auto Logout
  (configurable session timeout)". Same feature, same Org Settings
  toggle, same deferred-logout-for-active-sessions behavior. The
  updated_fallback bucket landed the EPA tickets here on the
  2026-08-27 mass component-edit timestamp, but the feature shipped
  in 4.28 (2026-07-17).
- KOB-51184 (Bluetooth Keyboard on iOS 26) — Bluetooth keyboard
  support and Bluetooth Bridge pairing were documented in 4.23. The
  area has not seen major changes since; likely dragged into this
  bucket by the 2026-08-27 mass component-edit timestamp.

Restricted ADB shell (KOB-54601 + KOB-54705):
- Dropped the intro paragraph + Highlights block; a single bullet
  per change reads cleaner.
- Dropped the self-reference to the August 14 release and the
  "significant policy shift" framing.
- Scope simplified from "public cloud and trial devices" to "Public
  Cloud devices" — title case matches UI; "trial" removed since
  trial users share the Public Cloud device pool.
- Toolbar bullet reworded from "Fixed the toolbar bypassing the
  restricted-shell policy" to "the toolbar now uses the same policy
  as the CLI" — same technical content, without framing that reads
  as a security bypass.

Appium AI enhancements (KOB-54607 through KOB-54645):
- Rewrote to six focused bullets, each with the actual config
  values customers need.
- KOB-54607 dropped from user-facing (system prompt refactor +
  default Text/Vision model switched to gpt-5.6-terra — customers
  benefit without any config change).
- KOB-54609 (server-wide coord-space) and KOB-54610 (per-session
  capability) merged into one bullet since they're the same
  feature at different scopes.
- KOB-54613 (LlmClient.Temperature removal) called out as a
  breaking change with a concrete migration example — anyone who
  set Temperature=0 needs to switch to
  TextExtraBody={"temperature": 0}.
- KOB-54645 reworded from "security tightening — prevents leaking
  a server-side key to a customer-controlled endpoint" to a plain
  description of the new behavior (session-provided base URL
  requires session-provided key). Same technical content, without
  the framing that implies the past state was insecure.

Small cleanups:
- Xiaomi bullet (KOB-54023): dropped `deviceidle` and `whitelist`
  jargon; framed by customer effect (device stays awake through
  long automation runs) rather than the Android system mechanism.
- KOB-54356 (Parallel Sessions report) TODO reworded to flag that
  expansion needs Asgard access — a reviewer with Asgard access
  needs to pull the chart type, filters, and Portal access
  location.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The prior header "Restricted ADB shell" reads oddly on these pages
since the actual customer-visible change is that the ADB shell is now
*more* permissive (Aug 14 expanded the allow list; Aug 28 flipped the
architecture to a deny list). Renamed both section headers to
"ADB shell on Public Cloud devices" — descriptive, scoped, no
contradiction with the bullets underneath.

Also aligned Aug 14's body-scope wording ("On Public Devices") with
the new header ("On Public Cloud devices") for consistency with the
Aug 28 body. "Private Devices" left as-is — that's the UI label
customers see for private-cloud devices.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants