docs: RELEASE-NOTES.md for v1.3.0 - #98
Merged
Merged
Conversation
Replaces the v1.2.0 notes, as each release does. Every figure is measured rather than recalled: 48 suites and 854 cases, counted the way scripts/draft-release-notes.mjs counts them (v1.2.0 that way is 40 and 599, which is what its notes say); the per-suite counts from each suite's own last line; the context windows by running both releases' catalog over the model ids; the token lifetimes from the backend's EditorToken; the plan each model starts at from the live pricing endpoint. The draft script itself could not be used: it refuses to run once the tag exists, and v1.3.0 was tagged first. So these notes land after the tag, as v1.2.0's did. Described relative to v1.2.0, not to this cycle's own review rounds — a state that only ever existed between two commits here is not something a user saw. One claim is flagged in the text as unproven on screen: the agent's browser preview. The chain is tested up to the call that opens the tab.
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The documentation accurately reflects the implemented behavior and test results.
Review effort: Balanced
Findings: None
What changed in this PR
Updates the release notes for LevelCode v1.3.0.
Changes:
- Documents cloud-session renewal and recovery improvements.
- Covers updated model capabilities and browser preview fixes.
- Summarizes fixes, limitations, and expanded test coverage.
| File | Description |
|---|---|
RELEASE-NOTES.md |
Replaces v1.2.0 notes with verified v1.3.0 release details. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.2.0 notes with v1.3.0's, as each release does. This is the text that goes into the GitHub release when it is published.
What it leads with
API 401: Signature has expired.Where the facts come from
scripts/draft-release-notes.mjscountscatalog.jsrun over the model idsEditorTokenand its refresh actionEverything is described relative to v1.2.0. States that only existed between two commits of this cycle's review rounds are left out: no user saw them.
Two things to know
No new settings or commands in this release, so those two sections are absent.