[dansleboby]

Summary

• Linux package in every release: CanonWebAPI-linux-x64.tar.gz (folder CanonWebAPI/): self-contained single-file Canon.API for Linux x64 (no .NET or ICU to install) with libEDSDK.so, plus install.sh, which installs it as the canonwebapi systemd service in /opt/canonwebapi (hardened unit), with a udev rule that gives the service user the Canon PTP cameras. The rule uses final assignments: 60-libgphoto2*.rules sorts after it and would give the camera back to plugdev at every replug, power-on or reboot. install.sh checks the system and the package before changing anything and fails when the service does not stay up; install.sh --uninstall removes everything. Manual updates (run the install.sh of the new archive).
• Package check: tools/Test-Package.ps1 starts a published package from a temporary copy and checks that /status answers (camera connected, or "No Canon camera detected"): it fails when the EDSDK library cannot be loaded.
• CI on Windows and Linux: both runners build and test, then publish and check their package (the published Windows executable was never run before a release).
• Atomic release pipeline: prepare (tag check, version) -> windows + linux in parallel (build, test, publish, check, archive) -> release with both packages and the AutoUpdater XML, only when both succeeded. The build jobs get a read-only token. workflow_dispatch runs a dry run that also downloads both packages and generates the XML in the release job, but creates no release and pushes nothing. The Windows package and the feed are unchanged (the generated XML is byte identical, UTF-8 BOM included).
• Fatal startup error exits with code 1 (it exited 0): systemd Restart=on-failure and launchers see it.
• Release 1.5.0.0 prepared: version, README upgrade note, changelog dated 2026-10-04. The tag is not pushed.

Design: specs/2026-10-04-linux-package-design.md, plan: specs/2026-10-04-linux-package-plan.md.

Test plan

• Local (Ubuntu 26.04): the archive built as in the release job lists the expected files (owned by root, executable Canon.API and install.sh); Test-Package.ps1 passes on the package and fails without libEDSDK.so; install.sh simulated without root (install, update keeping appsettings.Local.json, re-run, double uninstall, missing package file); bash -n, shellcheck, udevadm verify, systemd-analyze verify clean; the release XML step produces the current docs/autoupdate.xml byte for byte.
• CI: build-and-test (Windows) and build-and-test-linux pass, including both package checks.
• install.sh on a real machine (Ubuntu 26.04) with the EOS R100:
  • service active and connected; camera device root:canonwebapi 0660 after the install and after two real power-ons (desktop user keeps its ACL);
  • tools/Test-Camera.ps1 against the service: 14/14 (live view, 4 captures in 1.2-1.3 s, 3 flash changes each followed by a capture, power cycle with the live view running, capture after it);
  • battery dead during the test: disconnection handled, service stayed up, reconnected when the camera came back;
  • update 1.4.0.0 -> 1.5.0.0: clean stop (camera session closed), logs kept, camera reconnected in 0.5 s;
  • uninstall removes the service, unit, rule, /opt/canonwebapi and the user; the camera returns to root:plugdev 0664.
• After merge: dry run of the "Release CanonWebAPI" workflow on main, then the v1.5.0.0 tag on the owner's go-ahead.

🤖 Generated with Claude Code