Repository navigation
Release v1.4.0: the notes, and the Welcome page says what the site says - #109
Merged
Merged
Conversation
To someone deciding whether an editor may go on a work machine, "hackable" reads as "can be hacked". The site stopped saying it on 2 October; the app still did, in five places a user reads: - the Welcome walkthrough: now the site's own line, "The AI code editor that keeps you in control" - the Customize panel's section: Customization - the customization extension's name, description and settings title The extension's id (levelcode-hackability) and its settings keys stay, so nothing that refers to them breaks. Code comments are untouched.
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Signature-verification guidance needs correction so users understand upgrade protection and key-rotation failures.
2 open findings
What changed in this PR
Prepares v1.4.0 release notes and aligns desktop onboarding and customization labels with the site's wording.
Changes:
- Documents release highlights, fixes, testing, and known limitations.
- Updates user-facing copy without changing extension IDs, settings keys, or commands.
| File | Description |
|---|---|
| RELEASE-NOTES.md | Replaces previous notes with v1.4.0 release details. |
| extensions/levelcode-hackability/package.json | Renames display labels to LevelCode Customization. |
| extensions/levelcode-ai/package.json | Updates the Welcome walkthrough description. |
| extensions/levelcode-ai/customize.js | Renames the panel section to Customization. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…t a key change does - Anyone who set extensions.verifySignature to false to get past the old refusal stays unchecked after upgrading: say so, and how to turn it back on. docs/EXTENSION-SIGNATURES.md asked for exactly this line in these notes. - A .vsix installed from a file is not checked. - The daily check cannot get ahead of a key change: extensions signed with a new key are refused until an update carries it. Say that, and what the check is for, instead of promising advance notice.
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.

Everything v1.4.0 needs before it is tagged. Two commits:
fix(copy): the app stops calling itself hackable. That word was in five places a user reads: the Welcome walkthrough (now the site's line, "The AI code editor that keeps you in control"), the Customize panel's section, and the customization extension's name, description and settings title (now LevelCode Customization). The extension's id and settings keys are unchanged, so nothing that refers to them breaks.docs: RELEASE-NOTES.md for v1.4.0. Written against v1.3.1, fromscripts/draft-release-notes.mjs 1.4.0for the facts (range, PRs, test counts) and the code for every claim. The highlights:Checked before tagging
Three changes in this release were never run in the real desktop editor, by their own PRs' accounts: #105's rework of the agent's file reads and writes, #104's diagrams and #108's Argon handling. Both runs below used the dev build (
vscode/.build/electron) as a throwaway instance, withdevelop's extension (179eb03) and a local stand-in model:scripts/diagram-editor-check.js: 19 / 19. The chat, an agent turn, a diagram painted in the webview in the theme, Full size, a linked box openingrouter.jsat line 4, and the session on disk.google/gemini-4-argon:write_filelands on disk and goes under review ("1 file changed").run_commandwaits for approval, then runs in the real shell, and its output (hello.txt,router.js) reaches the model.reasoning: { effort: "medium" }andmax_tokens: 32768.scripts/test-extensions.shon this branch: 126 files, macOS, Node 24.Not run: a live model in the editor, the packaged app (CI builds and smoke-tests that), and the Linux suite run (Docker was unavailable here; the release workflow's test job runs on Linux).
After merging (from docs/RELEASING.md §7)
develop, thengit tag v1.4.0 && git push --tags. CI builds both arches and opens a draft release with the unsigned zips.make-dmg.shfor arm64 and x64, then upload the dmgs and update zips and drop the unsigned zips.gh release edit v1.4.0 --draft=false --notes-file RELEASE-NOTES.md. Run it from a checkout that has this PR merged and pulled; v1.3.1 went out with v1.3.0's notes. Afterwards,gh release view v1.4.0 --json body --jq '.body[0:40]'should start with# LevelCode v1.4.0.