Cause racine de l'ecran noir apres mise a jour : l'etag faible de @fastify/static derive de
taille+mtime, et npm pack fige le mtime de tout le tarball a une date constante (1985-10-26). Deux
index.html de versions differentes mais de meme taille partageaient donc le meme etag : le client
recevait un 304, gardait son index perime, et demandait des /assets/<hash> disparus ; le fallback SPA
repondait index.html en text/html pour ces modules, le navigateur refusait le script, rien ne peignait.

- fix(server): index.html et tous les fichiers non haches servis en no-store, validation
  conditionnelle desactivee (etag/lastModified) pour qu'un client bloque sur un index perime se
  repare seul ; /assets/ (noms haches) passent en immutable un an
- feat(web): copier/coller dans le terminal xterm, dont la selection n'est pas une selection DOM :
  Ctrl+Maj+C / Ctrl+Maj+V, Cmd+C / Cmd+V sur macOS, Ctrl+Inser / Maj+Inser, plus interception de
  l'evenement DOM copy pour que le Copier natif fonctionne. Ctrl+C reste SIGINT
- fix(web): script anti-FOUC sorti dans /theme-boot.js, la CSP script-src 'self' du daemon refusait
  de l'executer inline (le theme n'etait donc pose qu'au montage de la SPA)
- feat(web): les worktrees d'un groupe se deplient sur leur arborescence de fichiers dans le panneau
  Groupes (meme composant et meme etat d'expansion que l'Explorateur), et un worktree ainsi deplie
  est desormais surveille en temps reel
- fix: octet nul litteral remplace par \0 dans trois sources (stores/ide.ts, GitPanel.vue,
  vscode/repos-tree.ts) : git et grep les traitaient comme binaires, leurs diffs etaient
  illisibles en revue et la garde CI lint-dashes (git grep -I) les sautait en silence
- test: cacheControlFor et clipboardIntent en tests purs, verify-clipboard.mjs (E2E Chromium CDP :
  copie, collage et SIGINT prouves par le presse-papier reel et par le systeme de fichiers),
  capture groups-dark-desktop ajoutee a verify-ui.mjs

2026-08-04 16:23:33 +02:00

8.1 KiB

Raw Blame History

Changelog

Notable changes to @johanleroy/git-arboretum (the Arboretum daemon). The VS Code extension keeps its own changelog in packages/vscode/CHANGELOG.md.

3.5.0

Fixes a black screen after every update, gives the web terminal a working copy & paste, and lets you browse a group's files without leaving the Groups panel. Fully additive, no protocol version bump.

No more black screen after an update. The embedded SPA is served by @fastify/static, whose weak etag derives from size + mtime, and npm pack pins the mtime of every file in the tarball to a constant (1985-10-26). Two different index.html of equal size therefore shared an etag: clients got a 304 Not Modified and kept an index referencing /assets/<hash> files that no longer existed. The fallback route then answered those module requests with index.html as text/html, the browser refused the script, and nothing painted. index.html and every other unhashed file are now served no-store with conditional validation disabled, so a client holding a stale copy repairs itself; hashed /assets/ are served immutable for a year.
Copy & paste in the terminal. xterm's selection is not a DOM selection, so the native Copy (the Electron Edit menu, the browser context menu) had nothing to copy and terminal output could not be retrieved at all. Ctrl+Shift+C / Ctrl+Shift+V (Cmd+C / Cmd+V on macOS, plus Ctrl+Insert / Shift+Insert) now copy the selection and paste the clipboard, and the DOM copy event is intercepted so the native Copy works too. Ctrl+C is deliberately untouched: it stays SIGINT.
Theme applied before the first paint again. The anti-FOUC script was inline in index.html, which the daemon's own CSP (script-src 'self') refused to execute; it moved to /theme-boot.js.
Browse files from the Groups panel. A group's worktrees expand into their file tree, the same component and the same expansion state as the Explorer, and those worktrees are now watched for real-time changes too.
Sources are text again. Three files embedded a literal NUL byte in a string separator, which made git and grep treat them as binary: their diffs were unreviewable and the lint-dashes CI guard (git grep -I) silently skipped them. Escaped as \0, same runtime value.

3.4.0

Visibility release: the real-time machinery is now actually armed, worktrees show what they are worth, and history is served. Fully additive, no protocol version bump.

Real-time that no longer depends on which panel is open. A live session now pins the FS watcher of its worktree, so a worktree an agent is writing into refreshes on its own even when nobody is looking at it (pinSession existed but was never called). On the client side, watch subscriptions moved out of the Git panel, which was unmounted as soon as you left its tab, taking the app's only subscription with it; they now follow what you actually look at (active worktree plus expanded repositories).
Reconnection no longer loses state. The protocol replays nothing, so every event missed during a WebSocket outage was lost for good. The client reloads repos, worktrees, sessions and settings whenever the connection comes back.
Session correlation by containment. A terminal started in a subdirectory of a worktree (which "Start the project" allows) and a group session covering a worktree through --add-dir are now listed under that worktree, instead of vanishing from the tree. The rule lives in @arboretum/shared, shared by the daemon, the web UI and the VS Code extension; the most specific worktree wins.
History API. GET /api/v1/repos/:id/worktrees/log serves the branch commits with the count of unpushed ones, and GET .../worktrees/diff?commit=<hash> the full diff of a commit (hash strictly validated, same size limits as file diffs). The UI unfolds them in place under the Git panel.
Full git counters where they matter. ahead/behind, staged, unstaged and conflict counts were only visible in the status bar, for the active worktree. They are now on every worktree row of the tree and of the Groups panel, with upstream and last commit in the tooltip. locked, prunable and an invalid repository are surfaced too.
Groups show their composition. A group lists its repositories with their worktrees and git state, its sessions (live and recent) and the directories a group session spans. Its colour tints those repos in the explorer.
Actionable 403 BAD_ORIGIN. The error now names the exact --allow-origin flag to add, and logs it. It is the first wall of any LAN or reverse-proxy access.
Windows support in the daemon. where.exe for CLI discovery, PowerShell as the project launch shell, a .cmd askpass so token-based HTTPS clone/push works, taskkill /T for process-tree termination, %APPDATA% for the data directory, and arboretum install registering a scheduled task.
UI fixes. Error toasts were painted behind modals (they are sticky, so they piled up invisible); on mobile, opening a terminal or switching activity had no visible effect; the dock could push the status bar out of the viewport; panels showed "nothing here" instead of a loading or error state; modals had no dialog role, focus trap or focus restore; the splitters are now keyboard operable; diff line numbers stay pinned while scrolling.

3.3.0

"Start the project": boot a project's long-running commands (dev server, API, database) in one click. Fully additive, no protocol or API change.

Launch commands per repo. A repo now carries reusable start commands (label, shell command, optional subdirectory), persisted as JSON and edited from the dashboard. They can be auto-detected from package.json scripts, a Procfile or a docker-compose file.
One terminal per command. POST /api/v1/repos/:id/launch resolves the target worktree server-side (the client never passes a raw path) and opens one managed terminal per enabled command, all sharing a launch run id so you can stop the whole set in one action. Each command runs in your interactive login shell (so npm, docker, nvm/asdf are on PATH) and the shell stays live after the command exits, keeping failures on screen.
Surfaces. Start a project from a repo or worktree menu, the sessions panel or the command palette. The VS Code extension exposes it too (see its changelog).

3.2.0

Visual overhaul: the web UI adopts the "Emerald" design system and gains a full theme system. No protocol or API change (fully additive, backward compatible).

Light and dark themes. A light / dark / system toggle (in the activity bar and in Settings), remembered across sessions and applied before the first paint (no flash of the wrong theme). The Monaco editor, the xterm terminals (now with a full 16-color ANSI palette) and the diffs all re-theme live.
Emerald design language. Self-hosted Inter + JetBrains Mono, an emerald accent, consistent rounded corners, mono status pills and dots, refined focus and text selection, thin scrollbars, and a terminal signature motif.
Marketing site aligned. git-arboretum.com now mirrors the app: the same tokens, fonts and theme toggle, with up-to-date IDE mockups.

3.1.0

The IDE becomes the single shell of the web UI; the legacy worktree-first dashboard is retired as the default surface (still reachable at /dashboard).
Desktop app metadata fixes (window logo on Debian / Wayland).

3.0.0

Multi-project IDE milestone: one workspace (route /ide, the default on desktop) holding every open project at once, a unified project / worktree / session tree, a tabbed Monaco editor with inline diffs, docked session terminals, and Git / Sessions / Groups panels. Ships as a native Electron desktop app (Linux, Windows, macOS) alongside the same web UI.

2.0.0

"Real worktree IDE" foundations: a pure git engine, a real-time file-system watcher, the file API, selective staging / discard / amend / fetch / pull, automatic session archival, real-time settings sync, and encrypted remote git services (GitHub / GitLab / Gitea) with HTTPS clone.

8.1 KiB Raw Blame History