- Windows services whose program lies in the install folder (Titano.Server
--install-service) are found in the registry and, through the Service
Control Manager, stopped before files are replaced (they join the
"programs running" prompt), started again after an upgrade that stopped
them, deleted when an upgrade drops their program and on uninstall. An
unelevated setup runs that step in an elevated copy (/SERVICES=...).
- The Server component installs for all users only (manifest allUsersOnly):
choosing it moves a new install to Program Files and disables "Just me"
with the reason; a per-user install cannot take it.
- Uninstall removes every HKCU Run value that starts a program in the folder
(the Uploader's "Start with Windows").
- A shortcut that already starts an existing program elsewhere is neither
retargeted nor logged, and a logged shortcut is deleted only while it
still starts a program of this folder, so the two products no longer
remove each other's "Titano Uploader" shortcuts.
- "Remove my data" lists and deletes only the data of this product's
programs that no other installed Titano product uses (the desktop app and
the Uploader share %LOCALAPPDATA%\Titano and its logs folder).
- The .titano file type is named in setup's language (Setup.FileType.*).
Setup tests run in Titano.App.Tests on Windows CI.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- The docker job waits for the Windows build and tests and pushes only :<v>;
publish moves :latest with imagetools once the GitHub release exists and the
tag is the newest stable one, so a failed or older re-published tag never
moves it.
- The GitHub release is created before the public repository content, so the
public SHA256SUMS never describes a release that does not exist.
- Stable release notes start from the previous stable tag.
- Raw links to the public repository follow its default branch.
- Public README and bug form name the Diagnostics row and its button.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- Quote the bug form's Version description (it did not parse, so GitHub offered no bug form at all).
- .github/scripts/check-yaml.rb parses workflows, the compose file and the public issue forms (and checks the form
shape); CI runs it on Linux and the release job runs it before publishing the forms.
- Builds and publishes pass TitanoReleasesRepo=$RELEASES_REPO, so binaries read the repository they are published to.
- Image links in the public repository point to the image the docker job pushed.
- The public repository content follows the newest stable release; older tags and pre-releases only get their
release, and an older stable tag is never marked Latest.
- Screenshot captures time out after 10 minutes; the perf summary reports missing timings.
- Public README names the in-app "Suggest a fix" link.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The step conditions read step-level env, which a step's own if cannot see:
signing never ran and every release went to this repository. Secrets now
surface as job-level HAS_* flags. The publish job sets up .NET for make-icon,
re-publishing a tag updates the existing release, the portable zip carries
portable.txt, and tags are validated before anything is built.
deploy/releases-repo holds the public README, EULA draft, SECURITY policy and
issue forms; release.yml copies them with the Unraid template, compose file,
screenshots, i18n and SHA256SUMS. The fixtures command reports missing
samples as warning annotations (--allow-missing) instead of a silent pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The connection-string test built options with the platform default,
which is SQLite on Windows, so it parsed a file path as a PostgreSQL
connection string. The server gains a log level setting
(TITANO_LOG_LEVEL, also in compose and the Unraid template); the test
servers log warnings only, which cuts the suite's output from 511 to 80
lines so failures stay findable in CI logs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The external docker/dockerfile:1 frontend is pulled from Docker Hub,
whose auth endpoint returned 502 and failed the image build. Nothing in
the Dockerfile needs it; base images come from mcr.microsoft.com.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- Titano.Ui: DESIGN.md tokens (dark/light), generated 16-px icon set,
styles for all standard controls, custom chrome window with snap
layouts, rail, job bar, Auto/manual slider, chips, toasts.
- Titano desktop shell with sections, Settings (language, theme),
About and a --capture screenshot mode.
- Titano Server skeleton: env/server.json configuration, self-signed
TLS with fingerprint, /health, /server/info, i18n endpoint and the
embedded admin panel; in-process server tests.
- Docker image (multi-arch, PUID/PGID, health check), compose file,
Unraid template; CI, release and nightly workflows; changelog tool.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC