release: git-arboretum 3.5.0 (cache SPA, copier/coller terminal, fichiers des groupes), desktop 0.2.1
CI / No em/en dashes (push) Successful in 3s
CI / Build & test (Node 24) (push) Successful in 10m50s
CI / Build & test (Node 22) (push) Successful in 11m2s
Release / Publish to Gitea npm registry (push) Successful in 10m56s
Desktop Release / Build Linux (AppImage + deb) (push) Successful in 13m21s
Desktop Release / Publish floating desktop-latest release (push) Successful in 11s
CI / Pack & boot smoke (Node 22) (push) Successful in 9m53s
Desktop Release / Build Windows (NSIS + portable) (push) Canceled after 0s
CI / No em/en dashes (push) Successful in 3s
CI / Build & test (Node 24) (push) Successful in 10m50s
CI / Build & test (Node 22) (push) Successful in 11m2s
Release / Publish to Gitea npm registry (push) Successful in 10m56s
Desktop Release / Build Linux (AppImage + deb) (push) Successful in 13m21s
Desktop Release / Publish floating desktop-latest release (push) Successful in 11s
CI / Pack & boot smoke (Node 22) (push) Successful in 9m53s
Desktop Release / Build Windows (NSIS + portable) (push) Canceled after 0s
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
This commit is contained in:
@@ -3,6 +3,33 @@
|
||||
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,
|
||||
|
||||
Reference in New Issue
Block a user