Skip to content

docs(release-notes): add Kobiton 4.26.4S standalone release notes#491

Open
tungmhoang wants to merge 4 commits into
mainfrom
docs/release-notes-4_26_4S
Open

docs(release-notes): add Kobiton 4.26.4S standalone release notes#491
tungmhoang wants to merge 4 commits into
mainfrom
docs/release-notes-4_26_4S

Conversation

@tungmhoang

@tungmhoang tungmhoang commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds the Kobiton 4.26.4S standalone release-notes page and wires it into the release-notes nav. Generated through the Robot Ranch (docs-workflow) release-note pipeline from the deployment log in .ai/project-specific/portal-deployments-may20-jun10.md (May 20 – June 10, 2026) plus normalized Jira evidence.

  • New page: docs/modules/release-notes/pages/all-releases/4_26_4S.adoc
  • Nav: added the entry above 4_26S.adoc in nav.adoc

Related issues

Pipeline (which ranch hands ran)

Step Ranch hand Outcome
Classify Valentine (jira-bucketer) Triaged 20 deployment rows; separated release-note candidates from internal/ops
Update vs new Scout (git-scout) Newest cloud page 4_26.adoc is dated May 9; these land after it → new page
Affected mentions Bloodhound Skipped — additive notes, no existing prose to drift
Clean source Scrubber Skipped — clean Markdown table + structured Jira, nothing to scrub
Fetch evidence Dish (jira-draft) Fetched + normalized 16 Jira tickets (all Released)
Draft Ledger (docs-writer) release-note mode draft
Style Style Sheriff Pass, 0 required fixes
Gate Gatekeeper Ready (1 intentional placeholder: release date)

Ticket → entry mapping (IDs omitted from public copy per release-note rules)

Features

  • KOB-52769 — Device-only view for live sessions
  • KOB-53093 — Guide AI-driven sessions from the device canvas (getUserInputEvents)

Bug fixes and improvements

  • KOB-53091, KOB-53267 — Appium/Python generated-script fixes
  • KOB-51850 — ADB shell am start for protected packages
  • KOB-52914 — clearer error for app versions with removed storage files
  • KOB-53274, KOB-53275 — OS build number in device modal + Device List search
  • KOB-53279 — manual-session command latency with multiple reconnects
  • KOB-53331, KOB-53325, KOB-53324 — MCP server tools
  • KOB-53218 — app-signing API error message
  • KOB-53326 — SSO sign-in invalid company name message

Excluded as internal / not user-visible: KOB-53351 (v1→v2 MCP endpoint migration), KOB-52724 (ai_tool_name telemetry), KOB-53009 (PostHog), KOB-52949 (CI workflow), KOB-52999 / KOB-52412 (image-tag bumps).

Reviewer action items

  • Confirm and fill the release date (placeholder in the page; deployments spanned May 20 – June 10, 2026).
  • Confirm whether 4.26.4S is the latest standalone page. 4_26S.adoc carries a :page-aliases: to 4_26_5S, so standalone-kobiton-four-latest.adoc was not repointed — adjust if 4.26.4S should be the standalone "latest".
  • KOB-52412 appears in the deployment log labeled "update image tags," but is referenced elsewhere as the Python pytest parent story — verify the intended classification.
  • KOB-51850: the fix addresses the am start "Unsupported command" rejection for protected packages. Launching Work Profile apps across users remains an Android security limitation and is intentionally not claimed as fixed.

🤖 Generated with Claude Code

Add the 4.26.4S standalone release-notes page covering portal deployments
from May 20 to June 10, 2026, and wire it into the release-notes nav.

Drafted via the Robot Ranch (docs-workflow) release-note pipeline from
normalized Jira evidence. Internal-only changes (MCP v1->v2 endpoint
migration, ai_tool_name telemetry, PostHog tracking, CI workflow, image-tag
bumps) were excluded as not user-visible.
@tungmhoang tungmhoang force-pushed the docs/release-notes-4_26_4S branch from 5c81068 to b2bee1b Compare June 17, 2026 08:10
@tungmhoang tungmhoang marked this pull request as draft June 17, 2026 08:12
@tungmhoang tungmhoang marked this pull request as ready for review June 18, 2026 07:50

@tiffany-kobiton tiffany-kobiton left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to let Erin have final say, but overall I think this looks good. Written in our brand style, clear callouts of user-facing changes. I think the note section at the end has the right level of detail, but I think the wording "These release notes pertain to:" makes it sound like only users on those specific versions will see these changes. If that's true then cool! Is it safe to assume nothing in this release broke compatibility between versions, like between versions of dC and S? Does that question make sense?

@erincbailey erincbailey left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for putting this together. Please see my suggested changes.

Comment thread docs/modules/release-notes/pages/all-releases/4_26_4S.adoc Outdated
Comment thread docs/modules/release-notes/pages/all-releases/4_26_4S.adoc Outdated
Comment thread docs/modules/release-notes/pages/all-releases/4_26_4S.adoc
Comment thread docs/modules/release-notes/pages/all-releases/4_26_4S.adoc
Comment thread docs/modules/release-notes/pages/all-releases/4_26_4S.adoc Outdated
Comment thread docs/modules/release-notes/pages/all-releases/4_26_4S.adoc Outdated
Comment thread docs/modules/release-notes/pages/all-releases/4_26_4S.adoc Outdated
Comment thread docs/modules/release-notes/pages/all-releases/4_26_4S.adoc Outdated
@tungmhoang

Copy link
Copy Markdown
Collaborator Author

Feedbacks addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants