Repository navigation
15 development
Build, test, publish, versioning, localization, code style. Related: 02 — Projects & Solution · 14 — Testing
- .NET SDK 11.0.x (
global.jsonpins11.0.100, roll-forward latestMajor, no prereleases). - Windows (the projects target
net11.0-windowsand use WPF/DPAPI).
# build everything (Windows, both TFMs)
dotnet build SimpleLauncher.sln -c Debug
dotnet build SimpleLauncher.sln -c Release
# build one project
dotnet build SimpleLauncher/SimpleLauncher.csproj -c Debug
dotnet build SimpleLauncher.Avalonia/SimpleLauncher.Avalonia.csproj -c Debug
# run unit tests — WPF (net11.0-windows) and Avalonia (net11.0, headless)
dotnet test SimpleLauncher.Tests/SimpleLauncher.Tests.csproj -c Debug
dotnet test SimpleLauncher.Avalonia.Tests/SimpleLauncher.Avalonia.Tests.csproj -c Debug
# fast local WPF run (skip live mount + network tests that need G:\/X:\/J:\ or internet)
dotnet test SimpleLauncher.Tests/SimpleLauncher.Tests.csproj -c Debug \
--filter "FullyQualifiedName!~IntegrationTests&FullyQualifiedName!~ApiConnectivity&FullyQualifiedName!~UrlValidation&FullyQualifiedName!~MountChd&FullyQualifiedName!~MountZip"
# WSL2 / Linux — Avalonia only (net11.0 TFM, no Windows desktop pack)
dotnet build SimpleLauncher.Avalonia/SimpleLauncher.Avalonia.csproj -c Debug -f net11.0
dotnet test SimpleLauncher.Avalonia.Tests/SimpleLauncher.Avalonia.Tests.csproj -c Debug
wsl dotnet test SimpleLauncher.Avalonia.Tests/SimpleLauncher.Avalonia.Tests.csproj -c DebugSee 14 — Testing for the fast/slow suite split. Tests are not run by CI (the suites include live endpoints and real app launches); verification stays local + WSL2. The GitHub Actions workflows only package releases and deploy the docs — see Continuous integration.
dotnet publish SimpleLauncher/SimpleLauncher.csproj -c Release -r win-x64
dotnet publish SimpleLauncher/SimpleLauncher.csproj -c Release -r win-arm64-
RuntimeIdentifiersarewin-x64;win-arm64; every bundled tool ships both variants (X.exe+X_arm64.exe) and is resolved per architecture at runtime (see 11 — Bundled Tools). - Release zip naming for updates:
release_{version}_{rid}.zip(the unified WPF + Avalonia payload) +updater_{rid}.zip(the singleUpdater.exeshared by both apps) (see 16 — Updater). - A
publish-check\folder with per-RID outputs is used locally to validate published payloads.
scripts/package-release.ps1 reproduces the unified release artifacts (also used by CI):
pwsh scripts/package-release.ps1 -Version 5.8.4
# -> artifacts\release\release_5.8.4_win-x64.zip, release_5.8.4_win-arm64.zip
# -> artifacts\release\updater_win-x64.zip, updater_win-arm64.zip
pwsh scripts/package-release.ps1 -Version 5.8.4 -BuildInstaller
# -> the same files plus
# artifacts\release\SimpleLauncher-5.8.4-win-x64-setup.exe
# artifacts\release\SimpleLauncher-5.8.4-win-arm64-setup.exe- The bundle places
SimpleLauncher.exe(WPF) andSimpleLauncher.Avalonia.exe(Avalonia) next to each other and ships one shared set of content files (images/,tools/,samples/,appsettings.json, …). Users choose which app to run. - Copies
LICENSE.txt,README.mdandWhatsNew.mdto the payload root (Copy-BundleDocuments). - Both apps are published framework-dependent (the .NET 11 Desktop Runtime is required on the target machine), so the payload carries no runtime: each is a single executable with its managed assemblies bundled (
PublishSingleFile=true,SelfContained=false), and the small set of native libraries it needs (SQLite for WPF; Skia/HarfBuzz/GLES/SQLite for Avalonia) stays next to the exe. The updater is published the same way but additionally bundles its Avalonia natives for self-extraction, soupdater_{rid}.zipis one self-sufficientUpdater.exethat also works on legacy WPF-only installs. - Validates the version against
SimpleLauncher.csproj(canonical),SimpleLauncher.Core.csproj, both app csproj files/manifests andSimpleLauncher.Avalonia.Updater.csprojbefore publishing. - Merges the two publish outputs and fails loudly when a shared file has different content (for example
appsettings.jsondrift);AppSettingsFilesAreIdenticalguards the two appsettings sources in the test suite. - Prunes the other architecture's bundled tools from the payload (plus the Linux-only extension-less
7zzbinary) and packagesUpdater.exewithLICENSE.txt,README.mdandWhatsNew.mdintoupdater_{rid}.zip(the updater's staging tree is cleaned before each publish so stale sidecars cannot accumulate). The per-RID tools (FindRomCover,RetroAchievementsSharp,SimpleXisoDrive,SimpleZipDrive, the studios andCHDMounter) keep only the targetwin-{x64,arm64}subfolder. - Prunes debug symbol files (
*.pdb) — never needed at runtime; the native SkiaSharp/HarfBuzzSharp symbols alone account for roughly 105 MB.
-BuildInstaller compiles a per-user Inno Setup installer from the same merged payload. It
requires Inno Setup 6.5+ (ISCC.exe on PATH, in the default install folder, or passed with
-IsccPath); CI installs it with Chocolatey before packaging.
-
Per-user install, default
%LocalAppData%\SimpleLauncher, no elevation for the app files. The user can pick another writable folder on the Select Destination page. -
.NET 11 bootstrap: Setup looks for a
Microsoft.WindowsDesktop.App\11.*folder underDOTNET_ROOT,%ProgramFiles%\dotnet(native and the matchingx64/arm64subfolder) or%LocalAppData%\Microsoft\dotnet. If it is missing, it offers to downloadwindowsdesktop-runtime-11.0-win-{x64,arm64}.exefrom Microsoft (or use an offline copy namedwindowsdesktop-runtime-11.0*-win-{x64,arm64}.exeplaced next to Setup), then elevates only that runtime installer.Noopens the Microsoft download page and keeps Setup on the Ready page so the user can retry. -
Uninstall keeps user data: Inno removes only the files it installed.
settings.dat,system.xml, logs and game media remain in the install folder; the quickstart/FAQ document how to delete them. - Setup and uninstall share the app's single-instance mutex, so a running app is closed before files are replaced (the built-in updater still handles normal in-app updates).
- The installer is unsigned like the rest of the release;
SHA256SUMS.txtis attached to the GitHub release anddocs/faq.mdexplains the SmartScreen prompt.
Local smoke test (installs to a scratch folder, keeps a fake data file, then uninstalls):
$setup = 'artifacts\release\SimpleLauncher-5.8.4-win-x64-setup.exe'
$target = 'D:\Temp\sl-install-test'
Start-Process $setup -ArgumentList '/VERYSILENT','/SUPPRESSMSGBOXES','/NORESTART','/NOICONS',"/DIR=$target" -Wait
New-Item -ItemType File -Path (Join-Path $target 'settings.dat') -Force | Out-Null
Start-Process (Join-Path $target 'unins000.exe') -ArgumentList '/VERYSILENT','/SUPPRESSMSGBOXES','/NORESTART' -Wait
Test-Path (Join-Path $target 'settings.dat') # True: user data keptscripts/package-release-linux.ps1 produces the portable Linux pairs (the asset names the
in-app updater looks up in the GitHub release):
pwsh scripts/package-release-linux.ps1 -Version 5.8.4 -BuildSelfContainedPayload
# -> artifacts\release\release_5.8.4_linux-x64.zip, release_5.8.4_linux-arm64.zip
# -> artifacts\release\release_5.8.4_linux-x64.tar.gz, release_5.8.4_linux-arm64.tar.gz
# -> artifacts\release\updater_linux-x64.zip, updater_linux-arm64.zip
# -> <WorkDir>\linux-x64\selfcontained, <WorkDir>\linux-arm64\selfcontainedPlanned for the next release cycle: native
.deband.rpmpackages are not part of this script or the release workflow yet. The target matrix, runtime/install-layout decisions and acceptance checklist are in 21 - Release Artifacts. Do not add them torelease.yml,package-dry-run.ymlorpublish-fallback-r2.ps1before that checklist is complete.
- The portable payload is published framework-dependent single-file for
net11.0(the .NET 11 runtime is required; managed assemblies are bundled into theSimpleLauncher.Avaloniabinary with only the native libraries beside it, mirroring the Windows exes); the standaloneUpdateris framework-dependent single-file as well. -
release_{version}_{rid}.tar.gzis the same payload in a tar archive whose entry modes are written explicitly (0755 for the executables, 0644 otherwise), sotar -xzfrestores the executable bits even when the archive was built on Windows. -
-BuildSelfContainedPayloadalso publishes a self-contained payload (the .NET 11 runtime travels with the app) for the AppImage/Flatpak packager, removes the framework-dependentUpdaterfrom it, prunes Windows-only files and applies Unix modes when the script runs on Linux. - Copies
LICENSE.txt,README.mdandWhatsNew.mdto every payload root (Copy-BundleDocuments, the same helper the Windows script uses). - Windows-only bundled tools are pruned (
tools/**/*.exe,tools/**/*.dll, the other architecture's7zz); the per-RID tools (FindRomCover,RetroAchievementsSharp,SimpleXisoDrive,SimpleZipDrive, the studios andCHDMounter) keep only the targetlinux-{x64,arm64}subfolder; the matching7zzstays as the 7-Zip extraction fallback. - ZIP files written on Windows cannot carry Unix permission bits through
unzip, so the script stamps the entries' external attributes (0755 forSimpleLauncher.Avalonia,Updater,RetroAchievementsSharpand7zz, 0644 otherwise) and patches the entries' "version made by" host system to Unix. Extracting withunziprestores the executable bits; the in-app updater preserves installed modes during a swap, applies the archive's mode to files an update adds for the first time, and re-applies the executable bit to a freshly downloaded updater.
scripts/package-linux-native.sh runs on a Linux build host (CI uses ubuntu-latest) and
turns the self-contained payload into the two store-style bundles:
./scripts/package-linux-native.sh \
--version 5.8.4 --rid linux-x64 \
--payload artifacts/publish-linux/linux-x64/selfcontained \
--output artifacts/release
# -> SimpleLauncher-5.8.4-linux-x64.AppImage
# -> SimpleLauncher-5.8.4-linux-x64.flatpak-
AppImage — builds an AppDir (
AppRun,.desktop, icon, payload underusr/bin), then runsappimagetool. The tool is downloaded on first use. Forlinux-arm64on an x86_64 host it usesARCH=aarch64plus the aarch64 type-2 runtime (--runtime-file), so the precompiled ARM64 payload can be packaged without ARM64 hardware. -
Flatpak —
flatpak build-init/build-finish/build-export/build-bundleonorg.freedesktop.Platform//25.08. The app runs the emulators on the host viaflatpak-spawn --host, has host filesystem access for ROMs/emulators/BIOS/config files, and exposesorg.a11y.Busfor screen readers. FUSE mounting is disabled inside the sandbox (the app uses its extraction/conversion fallbacks) because a sandbox mount is not visible to host emulators. - Cross-architecture: both arm64 artifacts are exported from the x86_64 host because the payload is already compiled and no target code is executed; CI installs the x86_64 and aarch64 Flatpak runtimes.
- Verified on Linux Mint 22.3 x64 (X11): AppImage launched and rendered, Flatpak installed and
launched, the Flatpak launched the host dummy emulator through
flatpak-spawn, and the portable tarball extracted with correct executable bits and ran with the .NET 11 runtime. The arm64 AppImage and Flatpak were built and structurally verified (aarch64 ELF runtime and payload, aarch64 OSTree commit). The AppImage was also built and launched natively on the Azurelinuxarm-testARM64 host (2026-11-19); the Flatpak was not run there because the guest lacksflatpak-builderand the 25.08 SDK.
scripts/package-release-macos.ps1 runs on macOS (CI uses the arm64 macos-15 runner) and
produces the Apple Silicon DMG:
pwsh scripts/package-release-macos.ps1 -Version 5.8.4
# -> artifacts/release/SimpleLauncher-5.8.4-osx-arm64.dmg- Publishes
net11.0 -r osx-arm64 --self-contained true(the .NET 11 runtime travels inside the.app) and lays it out asSimple Launcher.app/Contents/MacOS. - Prunes the bundled
tools/tree and theUpdater: there are no macOS payloads for the bundled tools, and macOS updates install the next DMG instead of using the in-app updater. - Generates
Info.plist(LSMinimumSystemVersion15.0, bundle idcom.purelogiccode.simplelauncher) and a.icnsfromSimpleLauncher.Avalonia/icon/icon.png. - Ad-hoc signs the bundle with
codesign -s -(skip with-NoAdHocSign); it is not Developer ID signed and not notarized, so no Apple Developer certificate is involved. - Creates a compressed
UDZODMG with an Applications shortcut and verifies its contents withhdiutil.
The secondary download fallback
(https://assets.purelogiccode.com/Simple%20Launcher/Simple%20Launcher/, read by the updater when
GitHub is unreachable or rate-limited) is backed by the Cloudflare R2 bucket
simplelauncher-thumbnails under the prefix Simple Launcher/Simple Launcher/.
After the packaging scripts have produced every asset (four Windows/Linux RIDs plus the Apple Silicon DMG), publish the fallback copy:
pwsh scripts/publish-fallback-r2.ps1 -Version 5.8.4- Reads
R2_*credentials from the environment or the gitignoredAGENTS.local.mdblock (see the local-only notes); never commit them. - Uploads the four
release_{version}_{rid}.zip, the two portable Linux tar.gz files, the fourupdater_{rid}.zipassets, the two AppImages, the two Flatpak bundles and the macOSSimpleLauncher-{version}-osx-arm64.dmg, verifies their public URLs, then updatesversion.txtlast, so clients never see a version before its assets exist. AppImages self-update from this copy, so they must be published with the rest. The publisher also refresheseasymode_macos_arm64.xmlfrom the source catalog. -
-DryRunprints the plan;-ReleaseDirselects a non-default package folder. - The manual
release.ymlworkflow runs this publisher automatically after creating/updating the GitHub release, using theR2_*repository secrets. Local/manual releases still run the script explicitly.
The Avalonia app targets both net11.0 (Linux) and net11.0-windows (Windows), so the
target framework must be specified when publishing:
dotnet publish SimpleLauncher.Avalonia/SimpleLauncher.Avalonia.csproj -c Release -f net11.0-windows -r win-x64
dotnet publish SimpleLauncher.Avalonia/SimpleLauncher.Avalonia.csproj -c Release -f net11.0-windows -r win-arm64
dotnet publish SimpleLauncher.Avalonia/SimpleLauncher.Avalonia.csproj -c Release -f net11.0 -r linux-x64
dotnet publish SimpleLauncher.Avalonia/SimpleLauncher.Avalonia.csproj -c Release -f net11.0 -r linux-arm64
# Verify the output includes the bundled tools + updater
ls SimpleLauncher.Avalonia/bin/Release/net11.0/linux-x64/publish/ | head -20
ls SimpleLauncher.Avalonia/bin/Release/net11.0-windows/win-x64/publish/Updater* 2>/dev/null | head- The
net11.0TFM is Linux/macOS-only (audio output uses ALSA + managed decoders). Publishing it with a Windows RID (-f net11.0 -r win-x64) is rejected by a build guard: theWINDOWSsymbol would not be defined, soPlaySoundEffectswould take the ALSA path and fail on Windows (DllNotFoundException: libasound, no Windows native binary is shipped). - MP3 and WAV sound effects need no native libraries on Linux/macOS (NLayer +
WaveFileReader); FLAC/Ogg/Opus use the systemlibsndfile(sudo apt install libsndfile1on Debian/Ubuntu). A missinglibsndfile/libasound, a missing audio device or a corrupt sound file is logged at Information level (never reported as a bug) and playback is skipped. - The Windows publish uses Media Foundation + WaveOut, so neither
libsndfilenor ALSA is needed there. - Windows-only features (F8 global hotkey, active-window screenshot) are compiled with
#if WINDOWS(defined only on thenet11.0-windowsTFM) and pullSystem.Drawing.Commonas a package reference conditional on that TFM; the tray icon is cross-platform. -
WSL2 smoke test (Linux): after
publish -f net11.0 -r linux-x64, run the binary under WSLg:wsl ./SimpleLauncher.Avalonia/bin/Release/net11.0/linux-x64/publish/SimpleLauncher.Avalonia— window 1280×800 should map, single-instance mutex enforces one instance, tray icon is NoOp on WSL2. The full headless fast suite also runs on WSL2 without a display:wsl dotnet test SimpleLauncher.Avalonia.Tests/... -c Debug(725 tests viaAvalonia.Headless; the same suite also runs natively on macOS).
Version 5.8.4 must stay in sync across:
-
SimpleLauncher\SimpleLauncher.csproj(AssemblyVersion,FileVersion,Version) -
SimpleLauncher.Core\SimpleLauncher.Core.csproj(same three) SimpleLauncher.Tests\SimpleLauncher.Tests.csproj-
SimpleLauncher\app.manifest(assemblyIdentity version) -
SimpleLauncher.Avalonia\SimpleLauncher.Avalonia.csproj(same three, matching the WPF app) -
SimpleLauncher.Avalonia\app.manifest(assemblyIdentity version) -
SimpleLauncher.Avalonia.Updater\SimpleLauncher.Avalonia.Updater.csproj(Version, matching the WPF app)
The test projects (SimpleLauncher.Tests, SimpleLauncher.Avalonia.Tests, SimpleLauncher.SlowTests,
SimpleLauncher.Avalonia.SlowTests) and SimpleLauncher.ResourceTranslator carry the same version
metadata for diagnostics; keep them aligned when bumping.
VersionConsistencyTests enforces the manifests, the Avalonia csproj/manifest and the shared
appsettings.json in local runs; scripts/package-release.ps1 validates all of the above when
packaging. Bump all of them together.
-
One shared pack set for both apps:
SimpleLauncher.Core\Localization\strings.{code}.json(ar, bn, de, en, es, fr, hi, id, it, ja, ko, nl, pt-BR, ru, tr, ur, vi, zh-Hans) — UTF-8 without BOM, 2-space indent,StringComparer.OrdinalIgnoreCasekey order.strings.en.jsonis the canonical key set (2671 keys, all files in full key parity). - Both apps embed the packs in their assemblies: Avalonia as manifest resources (
SimpleLauncher.Avalonia.Resources.strings.{code}.json, loaded byLocalizationServiceviaAssembly.GetManifestResourceStream; no looseResourcesfolder ships); the WPF app as pack resources (resources/strings.{code}.jsoninSimpleLauncher.g.resources, via<Resource Include="..\SimpleLauncher.Core\Localization\strings.*.json" />inSimpleLauncher.csproj) withApp.ApplyLanguagebuilding the WPF languageResourceDictionaryfrom the JSON, resolving codes likept-br/zh-hanscase-insensitively. -
SimpleLauncher.ResourceTranslator(OpenRouter API, defaultz-ai/glm-5.3-flash) translates missing keys into the shared packs; see its README. - Unit tests guard against common translation issues: keys used in source but missing from English (auto-added with fallbacks), duplicate keys, mismatched fallbacks, empty values, key parity and key counts.
- WPF:
DetectMissingResourceProviderKeysTestsandDetectMissingResourceStringsTestsscan the WPF sources (_resourceProvider.GetString(...),TryFindResource(...)) and auto-add missing keys tostrings.en.json;DetectDuplicateResourceKeysTests,DetectAlphabeticalOrderingTests,ResourceFileLoadingTestsandLocalizationResourcePackagingTestscover the packs and the embedded payload. - Avalonia:
DetectMissingResourceStringsTestsscans the Avalonia source (.csGetString(...)calls and.axaml{ext:Translate Key}usages) and auto-adds missing keys;LocalizationTests.EveryLanguageFileSharesTheEnglishKeySetfails with a per-language missing-key list when files are out of sync. - The WPF and Avalonia auto-add tests mutate the same
strings.en.json; they serialize writes with a cross-process named mutex, so the suites are safe to run in parallel.
- WPF:
- Add a new language: create
strings.{code}.json(UTF-8 without BOM + sorted), add the code toLanguageMenuService(WPF) andLocalizationService.AvailableLanguages/AvaloniaLanguageMenuService(Avalonia), run the translator, and update the resource-key tests if needed.
-
Meziantou.Analyzer 3.0.315, Microsoft.CodeAnalysis.NetAnalyzers 10.0.402 and Roslynator.Analyzers 5.0.1 (all
PrivateAssets). -
Nullableenabled everywhere;LangVersion 15; implicit usings + globalusing System.IO; using System.Net.Http; using Serilog;. -
NoWarnin app:NU1903;CS0436. - Tests must satisfy the analyzers (e.g.
StringComparisonoverloads on string assertions). -
Every regex must specify a match timeout (Meziantou
MA0009):[GeneratedRegex(pattern, options, 1000)](add a culture before the timeout only when needed:[GeneratedRegex(pattern, options, 1000, "pt-BR")]), and pass aTimeSpan/milliseconds tonew Regex(...)and staticRegex.Match/IsMatch/Replace/Split/Matchescalls.Regex.Escape/Unescapeneed no timeout. - Conventions observed in the codebase: services take Serilog
ILogger; UI services use the host-interface pattern (Initialize(host)) instead of receiving windows; ViewModels use CommunityToolkit.Mvvm.
GitHub Actions builds the solution, packages releases and deploys documentation — it never runs the test suites (they include live endpoints and real app launches; run them locally).
| Workflow | Trigger | What it does |
|---|---|---|
.github/workflows/ci.yml |
push to master (non-docs paths) and pull requests |
Build-only: full SimpleLauncher.sln Debug and Release builds on windows-latest, plus the Avalonia net11.0 Debug/Release and updater net11.0 builds on ubuntu-latest. All builds use -warnaserror. Never runs tests. |
.github/workflows/package-dry-run.yml |
push/PR touching the app projects or packaging scripts (or manual) | Packages every release asset with the same scripts as the release workflow (Windows, Linux and the macOS DMG on macos-15), uploads the archives as workflow artifacts and verifies the Linux payload layout/executable bits and the DMG bundle layout — without creating a GitHub release. The version is read from SimpleLauncher/SimpleLauncher.csproj. |
.github/workflows/release.yml |
manual (workflow_dispatch) with a version |
Packages the unified WPF + Avalonia bundle for win-x64 + win-arm64 via scripts/package-release.ps1, the Linux bundles for linux-x64 + linux-arm64, and the Apple Silicon osx-arm64 DMG via scripts/package-release-macos.ps1; uploads the artifacts and creates/updates the release{version} GitHub release with every Windows/Linux/macOS asset. Options: skip release creation, provide custom release notes. |
.github/workflows/docs.yml |
push to master touching docs/** (or manual) |
Deploys GitHub Pages from docs/ and syncs the wiki via scripts/sync-wiki.py. |
master requires the two build checks from ci.yml for pull-request merges (direct pushes are
still allowed). The required contexts are the job names Build solution (Windows) and
Build Avalonia net11.0 (Linux) — keep them stable when editing the workflow.
To publish a release: bump the version everywhere (see Versioning), commit and push, then run Actions → Publish release → Run workflow with the new version.
The docs\ folder is published in two places:
The site is served from docs/ as a static landing page plus the docsify documentation (client-side rendering, no build step):
- Enable once in repo settings: Settings → Pages → Build and deployment → Source: GitHub Actions.
- The
docs.ymlworkflow deploysdocs/on every push tomasterthat touches docs (or manually). - URLs: landing page
https://purelogiccode.github.io/SimpleLauncher/, docshttps://purelogiccode.github.io/SimpleLauncher/docs.html.
docs/index.html (landing page), docs/landing.css / docs/landing.js (landing assets), docs/analytics.js + docs/analytics-config.js (opt-in cookie-free analytics), docs/media/ (screenshots, 20-second tour, OG image), docs/docs.html (docsify loader), docs/site.css (the docs dark/light theme), docs/_sidebar.md (TOC) and docs/.nojekyll are the site assets. The landing page redirects old #/... documentation links to docs.html#/.... To enable analytics, set the GoatCounter code or Plausible domain in docs/analytics-config.js and redeploy; while provider is none, no analytics requests are made. docs/_sidebar.md is the single source for both side menus: docsify reads it directly, and the wiki sync preserves its headings, group labels and order when it writes _Sidebar.md. docs/parameters.md and docs/manual-tests.md are copies kept for the site and wiki:
-
docs/parameters.md←SimpleLauncher/parameters.md— refresh it whenever the canonical file changes. -
docs/manual-tests.md←ManualTests.md(repo root) — refresh likewise.
The wiki is a separate git repo (SimpleLauncher.wiki.git); the default GITHUB_TOKEN cannot push to it, so the docs.yml workflow syncs it with a WIKI_PAT secret (classic PAT, repo scope). Without that secret the wiki job warns and skips.
python scripts/sync-wiki.py --dry-run # preview
python scripts/sync-wiki.py # clone/pull, rewrite, commit, pushThe script maps docs/README.md → Home, copies all docs/NN-*.md as pages, and protects the parameters page (https://github.com/purelogiccode/SimpleLauncher/wiki/parameters) — the app opens this URL (EditSystemWindow.xaml.cs, config key WikiParametersUrl), so it is never deleted and is refreshed from docs/parameters.md. Stale pages are deleted, _Sidebar.md is regenerated, and markdown links are rewritten to the flat wiki namespace.
- Implement features/fixes; keep
WhatsNew.mdupdated with a release section. - Bump version in the places listed under Versioning.
- Run the fast suites during iteration; run both slow suites before deploying (see 14 — Testing).
- Run Actions → Publish release with the new version — it packages the Windows and Linux RIDs (
release_{version}_{rid}.zip+updater_{rid}.zipforwin-x64,win-arm64,linux-x64,linux-arm64) and creates the GitHub release. Locally,pwsh scripts/package-release.ps1 -Version <version>andpwsh scripts/package-release-linux.ps1 -Version <version>produce the same packages. The workflow can also be run with Create or update the GitHub release unchecked to only build the zips as workflow artifacts. The optional release notes input is written into the release body (for example the currentWhatsNew.mdsection). - The in-app updater and silent update check use the GitHub
releases/latestAPI, with an automatic fallback to the secondary server (assets.purelogiccode.com/…/version.txt+ the hosted packages) when GitHub is unreachable or rate-limited (HTTP 403/429). Keepversion.txtand the hosted packages on that server in sync with each release — they are maintained outside this repository.