Conversation
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.
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The notes incorrectly state that launch always stops when macOS routing cannot be confirmed.
Review effort: Balanced
Findings: 1
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.
|
|
||
| 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

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
Where the facts come from
scripts/draft-release-notes.mjscountswebviewCss.test.jsfrom v1.3.1 run against v1.3.0's chat page: it failsdocs/CHAT-TYPOGRAPHY.md, as recorded with the fixThree things to know
No new settings or commands in this release, so those two sections are absent.