Skip to content

docs: RELEASE-NOTES.md for v1.3.1 - #101

Closed
ndemianc wants to merge 1 commit into
developfrom
docs/release-notes-1.3.1
Closed

ndemianc wants to merge 1 commit into
developfrom
docs/release-notes-1.3.1

Conversation

@ndemianc

@ndemianc ndemianc commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Replaces the v1.3.0 notes with v1.3.1's. This is the text that goes into the GitHub release when it is published.

What it leads with

  1. The composer stays put. Past a conversation's first long turn, scrolling beyond the end of the transcript slid the whole chat up over a blank page. It has done that since v1.1.0.
  2. Running from source: the dev editor is its own app. A sign-in started there comes back there.
  3. A build is checked for the identity it ships with.

Where the facts come from

Claim Measured how
49 suites, 892 cases; v1.3.0 was 48 and 854 every suite run at both tags, counted the way scripts/draft-release-notes.mjs counts
The fault dates from v1.1.0 the chat page read at each tag: the label is out of flow from v1.1.0, the transcript is positioned only at v1.3.1
The new guard catches the old page webviewCss.test.js from v1.3.1 run against v1.3.0's chat page: it fails
The scroll measurements docs/CHAT-TYPOGRAPHY.md, as recorded with the fix
The identity check ran on both architectures this release's build log

Three things to know

  • One sentence states production configuration: that LevelCode Cloud does not accept the dev scheme. It follows from the setting being off by default. If production has been opted in, that sentence and the matching entry under "Not in this release" need to change.
  • The scroll fix was measured in Chromium, not in a packaged build. The notes say so. It is worth one look in the signed app before publishing.
  • The draft script could not be used. v1.3.1 was tagged first, so these notes land after the tag.

No new settings or commands in this release, so those two sections are absent.

Replaces the v1.3.0 notes, as each release does.

One fix a user feels — the chat no longer slides away when you scroll past the
end of the transcript — and, for people who run from source, the dev editor's
own identity and the build check that goes with it.

Measured, not recalled: 49 suites and 892 cases, counted the way
scripts/draft-release-notes.mjs counts them (v1.3.0 that way is 48 and 854,
which is what its notes say). The scroll fix's figures are the ones in
docs/CHAT-TYPOGRAPHY.md; that the fault dates from v1.1.0 is read off the chat
page at each tag, and the new guard fails on v1.3.0's page. The identity check
is in this release's build log for both architectures.

The draft script could not be used: v1.3.1 was tagged first, so these notes
land after the tag, as the last two did.

Said plainly in the text, because it is new and follows from the dev scheme
being off by default: a source build cannot sign in to LevelCode Cloud.
Copilot AI balanced review requested due to automatic review settings October 4, 2026 21:39

Copilot AI 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.

Copilot review overview

🟡 Changes recommended

The notes incorrectly state that launch always stops when macOS routing cannot be confirmed.

Review effort: Balanced
Findings: 1 Low severity

Open (1)
What changed in this PR

Updates release notes for v1.3.1, covering the chat scrolling fix and development app identity safeguards.

Changes:

  • Documents the fixed chat transcript scrolling behavior.
  • Explains separate development and release identities.
  • Updates test coverage and changelog details.
File Description
RELEASE-NOTES.md Replaces v1.3.0 notes with v1.3.1 release documentation.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread RELEASE-NOTES.md

v1.2.0 had no entry for any of them and fell back to a guess: a 200k-token window for all three, and no images for Astra. In gateway mode that meant the model picker offered Astra while the composer refused your screenshot, and the context meter was sized for a fifth of the real window.
- **It is set on every launch,** in the two places it lives: what the editor believes at runtime, and what macOS believes about the dev bundle. Both or neither — the two files change as one change, and a failure half-way is undone.
- **The launch waits for macOS to agree.** After registering the bundle, the script asks macOS which app opens `levelcode-dev://` and stops unless the answer is this bundle. Being told about a bundle is not the same as agreeing to use it: one under a temporary folder is registered and never chosen.
@ndemianc ndemianc closed this Oct 4, 2026
@ndemianc
ndemianc deleted the docs/release-notes-1.3.1 branch October 4, 2026 21:42
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.

2 participants