Commit Graph

2 Commits

Author SHA1 Message Date
bd76e53570 docs(ci): documenter la portée write:repository requise de NPM_TOKEN
All checks were successful
CI / Build & test (Node 22) (push) Successful in 10m15s
CI / Build & test (Node 24) (push) Successful in 10m10s
CI / No em/en dashes (push) Successful in 3s
Desktop Release / Build Linux (AppImage + deb) (push) Successful in 14m1s
CI / Pack & boot smoke (Node 22) (push) Successful in 10m5s
L'attache des installeurs/VSIX à la release Gitea réutilise NPM_TOKEN ; ce
token doit porter write:repository EN PLUS de write:package, sinon l'API
release renvoie 403 (l'étape est best-effort, non bloquante : les artefacts
restent disponibles via upload-artifact).
2026-07-17 20:42:21 +02:00
1299b1b349 ci(desktop): workflow de release (C6) sur tag desktop-v*
Some checks failed
CI / Build & test (Node 24) (push) Has been cancelled
CI / Pack & boot smoke (Node 22) (push) Has been cancelled
CI / No em/en dashes (push) Has been cancelled
CI / Build & test (Node 22) (push) Has been cancelled
.gitea/workflows/desktop-release.yml : garde-fou tag==version (packages/desktop), npm ci racine + npm ci desktop (hors workspaces), npm run dist:linux (AppImage+deb), artefacts + attachement des installeurs et de latest-linux.yml (auto-update) à la release Gitea via NPM_TOKEN. Windows/macOS : build manuel sur ces OS (README desktop). N'affecte aucun workflow existant (tag desktop-v* distinct de v* et vscode-v*).
2026-07-17 18:05:36 +02:00