- Screenshots: a capture that exits with an error or writes nothing fails the job
(the pictures it wrote are still published); the new "Screenshot diff" step
compares them with tests/visual/baselines, fails beyond the tolerance, warns
once for screens without a baseline and uploads the diff images.
- installer (windows-latest): publishes App, Uploader and Setup (self-contained
single file, no ReadyToRun), packs Titano 1.0.0 (with an extra legacy.txt),
Titano 1.0.1 and the Uploader installer, and runs
.github/scripts/installer-test.ps1: argument and not-installed exit codes,
silent install into a folder with a space, Add/Remove Programs, shortcuts and
the .titano file type, the installed programs drawing their screens, upgrade in
place removing legacy.txt, uninstall removing itself, user data kept, the
Uploader installer; the setup logs are printed whatever happens. The script
now resolves its paths from the PowerShell location.
- PostgreSQL 16/17: postgres-ci-setup.sh prepares the service container and the
job exports the MD5, cleartext, trust, TLS and root-certificate variables.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
- New Titano.Tools.Tests program (CI and release run it): the warning annotation
escapes workflow-command characters, and a missing fixture fails the command
unless --allow-missing is given.
- ARCHITECTURE, STATUS, CHANGELOG and README describe the portable update
package, resumable and cancellable download, the release ordering, the
rebuild gate in the §1.1 shape and the new numbers.
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
ARCHITECTURE gains the module map, hosts, job kinds with their handlers, the
data flow and the extension points; STATUS records the measured performance
gates and the Phase 8 next steps; CHANGELOG summarises everything built
under Unreleased; README covers build, tests, CI, the release process, the
secrets and how to bootstrap the public releases repository.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC