Release-notes: draft post-4.28 collection doc [review structure] - #555
Release-notes: draft post-4.28 collection doc [review structure]#555tiffany-kobiton wants to merge 4 commits into
Conversation
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>
Release-note entry migrated into the post-4.28 collection doc via PR #555. Scoping this PR to the product-doc change on install-an-app.adoc only. TODO comment retained pending independent verification against a released build. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Release-note entry migrated into the post-4.28 collection doc via PR #555. Scoping this PR to the product-doc changes on start-a-mixed-session.adoc and test-cases.adoc only. 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].
erincbailey
left a comment
There was a problem hiding this comment.
Just a few notes.
I couldn't see this in the preview - not sure if it's because it is a few days old?
Also - how do I read the Reviewer Notes - are they telling me things that are not being done for a particular section? ARe they before a section after? Just trying to figure out context if random or not.
| // (Force offline outdated deviceConnect, Auto upgrade deviceConnect feature) are held for a | ||
| // separate pass. No Robot Ranch draft PR was generated for this ticket — sourced from Slack. | ||
|
|
||
| == Device management |
There was a problem hiding this comment.
I know it's on the Device Management page. But, this is more about Kobiton version management. Should we update the title?
| @@ -0,0 +1,70 @@ | |||
| = Release Notes | |||
| :navtitle: Release notes | |||
There was a problem hiding this comment.
Is the navtitle what shows up in the navigation? Should it be more specific - like the date August 14, 2026 or more in the build format 260814?
| - The Test Case preserves the original recorded order across the manual and automation steps, and tags each step with its source. | ||
| - Convert from Session Explorer or from the *+New Test Case* pop-up on the Test Cases list page. Search for eligible sessions with `type:mixed`. | ||
| - Test Cases converted from a mixed session show *Mixed* as the Source type. | ||
| - A Revisit replays each step through the execution path that matches its source and reports per-step results. Steps with no replayable equivalent, such as an unsupported Appium endpoint, are skipped with a reason and the run continues. |
There was a problem hiding this comment.
Instead of Revisit - can we use "A test run" since that's the terminology in the UI?
Summary
docs/modules/release-notes/pages/all-releases/2026-08-14.adoc.Release Notes), italic date under it, per-release-date sectioning (== 2026.07.28,== 2026.08.10,== Target release TBD), and new-features vs improvements-and-fixes classification are all flagged inline for reviewer input.install-an-app.adoc) and Update Test Cases and add Start Mixed Session #549 (start-a-mixed-session.adoc,test-cases.adoc) are not applied here — they stay parked on their source PRs for a separate review pass.Entries included
== 2026.07.28— Device passcode== 2026.08.10— Device management== Target release TBD— Security Banner== Target release TBD— Scriptless Test Runs== Target release TBD— Device details== Target release TBD— Convert a mixed session…Open questions for reviewer
==sectioning vs alternative structures (rolling monthly page? one CI/CD page?)Target release TBDentries should ship at all, or wait until each ships and joins its own dated sectionnav.adoc— not updated; sidebar placement pending structural decisionsTest plan
organization:change-the-login-message.adoc)nav.adocupdate before publishing🤖 Generated with Claude Code