tsuyoshi-otake/sakura-editor-next v3.1.0-build.7221

Sakura Editor NEXT v3.1.0 build 7221

on GitHub

Sakura Editor NEXT v3.1.0 build 7221

This prerelease contains the Issue #19 Source Control work, the Issue #18 Editor Core component work, and the Issue #17 workbench repaint fix through commit ab9cccf59.

Highlights

• Source Control is carried through to a safe Git workflow: the view and the status bar name the repository and the branch, staging, diff review, commit/amend/undo, and the nine remote commands (git.fetch, git.fetchPrune, git.fetchAll, git.pull, git.pullRebase, git.push, git.sync, git.syncRebase, git.publish) all have real executors. Every failure is typed instead of silent.
• The Git and API commands are registered under the built-in vscode.git extension's own command IDs, titles, menu groups, and ordering, so the commands are where a VS Code user expects them. Every divergence forced by a platform constraint is recorded in sakura_core/workbench/scm/CLAUDE.md.
• git.checkout / git.checkoutDetached / git.branch / git.branchFrom reproduce upstream's pickers and its remote-head tracking lookup, so checking out a remote head switches to the tracking branch instead of detaching HEAD.
• git.openChange renders the comparison natively through the new CDiffSurface; git.stageSelectedRanges / git.unstageSelectedRanges write the complete new index-entry content with hash-object --path plus update-index --cacheinfo rather than generating a patch.
• Every git child process runs through one bounded, cancellable runner with GIT_TERMINAL_PROMPT=0, so an empty change list means "clean" only when the refresh actually succeeded, and a credential prompt cannot hang a fetch.
• A committed layout change now repaints the whole workbench frame, which removes the stale-pixel corruption measured on the first bottom-Panel open and on frame resize (Issue #17).
• Editor Core gains L4 component boundaries, a semantic debt baseline with a ratchet, and an extracted selection-phase leaf component (Issue #18).
• version.h is now regenerated when HEAD moves, so the shipped binary reports the commit it was actually built from. The previous build reported a commit hash from an earlier HEAD.

Verification

• x64 Release solution rebuilt from scratch and packaged with 0 build errors.
• Release version: 3.1.0.7221 (ab9cccf5), sakura.exe 7,905,792 bytes.
• Native unattended suite (documented UI/integration exclusion filter) against the Release tests1.exe: 2,801 tests from 320 suites ran; 2,799 passed; 2 measurement-only tests skipped; 0 failed.
• Python build-tool suite: 130 tests passed.
• Assembly listings were regenerated in full for this build rather than incrementally, so the Asm package covers the whole binary.
• Six ZIP packages and the raw x64 installer were produced and SHA-256 checked before upload.
• The installer was reinstalled per-user on a developer machine and smoke-launched with a throwaway profile: the main window was created, closed cleanly with exit code 0, and left no surviving process or profile directory.
• Build and test child-process cleanup was verified after every run.

Tracking

Source Control work continues in Issue #19; the Editor Core component gates remain in Issue #18. This release does not claim those gates are complete.