Skip to content
DP-RELEASEReviewed · 2026-11-19Desktop 1.8 · Companion 1.1.1Lire en français

Versions and publication ​

Versions and qualification ​

versions.json links desktop 1.8.0, Companion 1.1.1, documentation and website 1.1.0. The exchange protocol remains version 1. Delivered tags and old downloads stay immutable. Use MAJOR for breaking changes, MINOR for compatible capabilities, PATCH for corrections. Annotated tags: desktop-vX.Y.Z-candidate.N, companion-vX.Y.Z-candidate.N, docs-vX.Y.Z.

Green CI does not qualify a real WoW cycle. The channel remains candidate until in-game smoke covers mail, import, posting, expiration/sale, character changes and combat.

From commit to Cloudflare ​

Every push and PR runs Windows/Linux quality, Node/Lua tests, coverage, mutations, Fallow, bilingual docs, shared assets and website link checks. Dependencies are locked and audited. External pull requests never receive deployment secrets.

On main, the workflow builds the Windows binary after rustfmt/tests/Clippy, attested archives, then the NSIS installer. Smoke installs to a temporary directory without shortcuts or registry integration, starts the included engine, verifies an upgrade preserving data, and an uninstall that retains those data.

The installer is uploaded to R2 under releases/<commit>/<run>-<attempt>/. The publicly downloaded bytes must match the tested SHA-256 before Pages publication. The website and FR/EN handbook are then checked on the public domain. Deployment or verification failure triggers rollback to the previous Pages deployment when one exists. releases/latest.json updates only after success. Production runs are serialized and a newer push does not interrupt an active publication.

Internal branches receive isolated Pages previews without replacing production downloads. Previews show downloads as pending rather than linking a fabricated installer.

One-time service configuration ​

Pages project donjons-et-pognons, R2 bucket donjons-et-pognons-downloads and domains are defined in deployment/config.json. Add GitHub Actions secrets CLOUDFLARE_ACCOUNT_ID and CLOUDFLARE_API_TOKEN once. Scope the token to the relevant account with Pages Edit and Workers R2 Storage Write. Never put secrets in source or command-line arguments. Actions environments are cloudflare-production and cloudflare-preview. Avoid required manual approval on each deployment when automatic publication is intended.

Repository configuration does not prove that secrets exist or that the latest remote run passed: inspect GitHub Actions and public checks. Revoke/rotate the token and update the secret when access changes.

Local builds ​

sh
npm ci --ignore-scripts
npm run verify
npm run build:native
npm run release
npm run test:packages
npm run build:installer
npm run test:installer
npm --prefix documentation ci --ignore-scripts
npm --prefix documentation run verify
npm run build:site
npm run test:site

The source digest binds reports and packages. ZIP entries are sorted with fixed dates; native Windows reproducibility is not claimed. Installer builds verify NSIS and WebView2 bootstrapper hashes; upstream changes require a reviewed update. Code signing is not configured.

References: Cloudflare CI, WebView2 distribution, NSIS.

A local-first advisor. Estimates stay visible.