Clients could not reach a server in a container whose ports are published as other host ports: the panel showed the container's ports, the template had no public HTTP port, and a bare host meant port 443. Public ports become panel settings, the panel shows the client address, both clients default to 8443, and an address that answers as another service is named as not a Chronos server (its certificate never offered for trust). The screenshot baselines are captured on the development PC and committed; measured values are fixed while the capture runs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- :latest follows the highest stable release, or the highest pre-release while none is stable (Chronos.Tools release-channels); bad tags are refused before anything is built.
- Unraid: CHRONOS_SPACE_PATH and the template's Array view show the array's free space; the write volume (cache) is shown apart; completions check the archive volume (507).
- Settings is a gear, docked at the foot of the admin sidebar; About is the last part of Settings on the desktop and the panel.
- Import > Folder > Whole folder: one sequence per format (desktop only).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
The owner renamed the product and moved the repository to the self-hosted
Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control,
and asked for Actions and a first automatic release with the server package
and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md).
- Chronos everywhere: a byte-exact rename of contents and paths, then a
per-language review of the forms the old name's ending had dictated.
- Gitea instead of GitHub: the update check, licence, issue and support
links read ChronosReleasesUrl; the update check takes the highest stable
version, offers a pre-release build its final release and reports a
repository it cannot see as a failed check. EULA, security policy and
Gitea issue forms live at the repository root.
- Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release,
nightly image and performance gates in the .NET SDK container with git
checkout and the system SQLite. The release cross-compiles the Windows
programs, checks their icon, version and DPI manifest, packs installers
and zips, publishes the Gitea release and pushes the server image
(REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows
runner (WINDOWS_RUNNER).
- New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the
docker-exec script, which Gitea's service containers do not allow; the
throw-away server runs without durability) and pe-check.
- Timed tests take their budget from TestTiming (CHRONOS_TEST_TIME_FACTOR,
3 on the shared runner; the weekly performance gates keep theirs).
BREAKING CHANGE: programs, settings, data folders, file types, environment
variables and the Docker image use the new name; nothing is migrated from
Titano, which never had a release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
F5 in VS Code now starts Titano, the Uploader and the server under the C#
extension's debugger, as well as the --capture runs, Titano.Tools and the test
programs. Each configuration builds in Debug first and starts the program's
.exe rather than its .dll, because the programs read Environment.ProcessPath
(Setup's payload, the Run keys and tray icons). The server's session keeps its
data and archive in out/debug/server instead of %ProgramData% and
C:\TitanoArchive.
The build tasks use no reused MSBuild nodes, whose cached drive-letter case
made every F5 build restore and C# Dev Kit reload, and keep MSB3026 (a copy
that succeeds on a retry) a warning so a file held for a moment no longer
stops F5.
Design-time builds skip the icon generation, which on a fresh clone ran a
Titano.Tools.dll that did not exist yet (MSB3073 in VS Code), and log WPF's
MC1000 about projects not built yet as a message.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 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