Skip to content

Release v1.4.0: the notes, and the Welcome page says what the site says - #109

Merged
ndemianc merged 4 commits into
developfrom
release/v1.4.0
Oct 15, 2026
Merged

ndemianc merged 4 commits into
developfrom
release/v1.4.0

Conversation

@ndemianc

Copy link
Copy Markdown
Contributor

Everything v1.4.0 needs before it is tagged. Two commits:

  1. 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.
  2. docs: RELEASE-NOTES.md for v1.4.0. Written against v1.3.1, from scripts/draft-release-notes.mjs 1.4.0 for 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, with develop'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 opening router.js at line 4, and the session on disk.
  • A release smoke run (a scratch script on the same harness, not committed): 13 / 13, with the model set to google/gemini-4-argon:
    • write_file lands on disk and goes under review ("1 file changed").
    • run_command waits for approval, then runs in the real shell, and its output (hello.txt, router.js) reaches the model.
    • The answer is shown, and the session is saved.
    • Undo takes the file back off the disk.
    • Every agent turn asked for reasoning: { effort: "medium" } and max_tokens: 32768.
    • Nothing threw.
  • Gate: scripts/test-extensions.sh on 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)

  1. Pull develop, then git tag v1.4.0 && git push --tags. CI builds both arches and opens a draft release with the unsigned zips.
  2. Sign and notarize locally with make-dmg.sh for arm64 and x64, then upload the dmgs and update zips and drop the unsigned zips.
  3. 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.

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.
Copilot AI balanced review requested due to automatic review settings October 15, 2026 01:48

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.

🟡 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.

Comment thread RELEASE-NOTES.md
Comment thread RELEASE-NOTES.md Outdated
…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.
@ndemianc
ndemianc merged commit d1abd38 into develop Oct 15, 2026
2 checks passed
@ndemianc
ndemianc deleted the release/v1.4.0 branch October 15, 2026 01:58
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