refactor!: rename Titano to Chronos and move CI and releases to Gitea #6

Merged
Alby96 merged 4 commits from claude/chronos-rename-gitea-migration-18c301 into main 2026-10-23 12:45:38 +02:00
Owner

Owner request of 2026-10-23 (docs/requests/2026-10-23-chronos-gitea.md): rename Titano to Chronos, move every GitHub reference to the self-hosted Gitea, and create Actions with the first automatic release (server package and Windows exe).

What changes

  • R1 – Chronos everywhere. Byte-exact rename of contents and paths (10,394 replacements in 1,744 files, 1,159 moved): projects, namespaces, CHRONOS_* variables, %LOCALAPPDATA%\Chronos, .chronos files, the chronos-server image. Translations reviewed per language for the grammar the old name dictated (80 strings: Finnish and Estonian cases, Turkish suffixes, Scandinavian genitives, Slavic and Baltic cases). No migration of old data: nothing was ever released.
  • R2 – Gitea. ChronosReleasesUrl (default https://gitea.encke-hake.ts.net/BalboSoft/Chronos) drives the update check, licence, issues and Add/Remove Programs links. The update check reads the stable releases and takes the highest version, offers a pre-release build its final release, and reports a repository it cannot see as a failed check. EULA.md and SECURITY.md at the root, issue forms in .gitea/ISSUE_TEMPLATE (Gitea schema). Releases go to this repository; a separate releases repository stays optional.
  • R3 – Gitea Actions. .gitea/workflows/ ci, release, docker (nightly), perf for the Linux act_runner: .NET SDK container, git checkout (no Node.js actions), no artifacts. The release cross-compiles the Windows programs on Linux, checks their icon/version/DPI manifest, packs the installers and zips, publishes the Gitea release and pushes the server image to the Gitea registry. Windows-only tests run in an opt-in windows job (WINDOWS_RUNNER).
  • New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the docker-exec script), pe-check.

Verification

  • Runner probed with a throw-away branch (deleted): cross-compiled Chronos.exe/Chronos.Setup.exe carry icon, version and PerMonitorV2 manifest; pack-installer runs on Linux; service containers resolve by name; the workflow token cannot sign in to the org registry.
  • Independent multi-angle review of the new tooling and workflows; 12 confirmed findings fixed (TLS key mode in postgres-ci, real TLS check, checksum order on re-publish, size check before publishing, highest version for :latest and the app, pre-release update, Docker clean-up after cancellation, link rewriting, Git Bash on Windows).
  • Local (Windows): Release build 0 warnings; Core 1195, Data 412, Server 157, Tools 38, Core.Windows 78 tests green; App update/setup tests green. Tests that enumerate this PC's disks (and the shell tests that start device detection) hang here on the original main code too, so they are environmental. i18n check, package guard, XAML lint and format check green.

Owner actions

  1. Secret REGISTRY_TOKEN (access token with package read/write) for the server image.
  2. Optional: make the organisation public; register a Windows runner and set WINDOWS_RUNNER.

🤖 Generated with Claude Code

Owner request of 2026-10-23 (`docs/requests/2026-10-23-chronos-gitea.md`): rename Titano to Chronos, move every GitHub reference to the self-hosted Gitea, and create Actions with the first automatic release (server package and Windows exe). ## What changes - **R1 – Chronos everywhere.** Byte-exact rename of contents and paths (10,394 replacements in 1,744 files, 1,159 moved): projects, namespaces, `CHRONOS_*` variables, `%LOCALAPPDATA%\Chronos`, `.chronos` files, the `chronos-server` image. Translations reviewed per language for the grammar the old name dictated (80 strings: Finnish and Estonian cases, Turkish suffixes, Scandinavian genitives, Slavic and Baltic cases). No migration of old data: nothing was ever released. - **R2 – Gitea.** `ChronosReleasesUrl` (default `https://gitea.encke-hake.ts.net/BalboSoft/Chronos`) drives the update check, licence, issues and Add/Remove Programs links. The update check reads the stable releases and takes the highest version, offers a pre-release build its final release, and reports a repository it cannot see as a failed check. `EULA.md` and `SECURITY.md` at the root, issue forms in `.gitea/ISSUE_TEMPLATE` (Gitea schema). Releases go to this repository; a separate releases repository stays optional. - **R3 – Gitea Actions.** `.gitea/workflows/` ci, release, docker (nightly), perf for the Linux act_runner: .NET SDK container, git checkout (no Node.js actions), no artifacts. The release cross-compiles the Windows programs on Linux, checks their icon/version/DPI manifest, packs the installers and zips, publishes the Gitea release and pushes the server image to the Gitea registry. Windows-only tests run in an opt-in `windows` job (`WINDOWS_RUNNER`). - New `Chronos.Tools` commands: `zip`, `gitea-release`, `postgres-ci` (replaces the docker-exec script), `pe-check`. ## Verification - Runner probed with a throw-away branch (deleted): cross-compiled `Chronos.exe`/`Chronos.Setup.exe` carry icon, version and PerMonitorV2 manifest; `pack-installer` runs on Linux; service containers resolve by name; the workflow token cannot sign in to the org registry. - Independent multi-angle review of the new tooling and workflows; 12 confirmed findings fixed (TLS key mode in postgres-ci, real TLS check, checksum order on re-publish, size check before publishing, highest version for `:latest` and the app, pre-release update, Docker clean-up after cancellation, link rewriting, Git Bash on Windows). - Local (Windows): Release build 0 warnings; Core 1195, Data 412, Server 157, Tools 38, Core.Windows 78 tests green; App update/setup tests green. Tests that enumerate this PC's disks (and the shell tests that start device detection) hang here on the original `main` code too, so they are environmental. i18n check, package guard, XAML lint and format check green. ## Owner actions 1. Secret `REGISTRY_TOKEN` (access token with package read/write) for the server image. 2. Optional: make the organisation public; register a Windows runner and set `WINDOWS_RUNNER`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Alby96 added 1 commit 2026-10-23 11:35:21 +02:00
refactor!: rename Titano to Chronos and move CI and releases to Gitea
CI / Build and test (pull_request) Failing after 2m3s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 4s
5f27a86406
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. 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) and
  pe-check.

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>
Alby96 added 1 commit 2026-10-23 11:43:39 +02:00
ci: install the system SQLite in the .NET SDK container
CI / Build and test (pull_request) Successful in 5m59s
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 5s
CI / PostgreSQL 16 integration (pull_request) Failing after 6m56s
CI / PostgreSQL 17 integration (pull_request) Failing after 3m47s
CI / Docker image (pull_request) Successful in 1m56s
7830fe46de
The Data and Server tests bind libsqlite3.so.0, which GitHub's runner had and
the SDK image does not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Alby96 added 1 commit 2026-10-23 12:05:43 +02:00
ci: run the throw-away PostgreSQL without durability
CI / Build and test (pull_request) Failing after 4m5s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 12s
f4800fd86d
On the runner's shared storage the 100k-frame bulk insert of the Phase 2
gate took 21-33 s against its 15 s budget: the timed tests should measure
the client's COPY path, not the host's disk flushes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Alby96 added 1 commit 2026-10-23 12:19:41 +02:00
test: stretch timed budgets on the shared CI runner
CI / Build and test (pull_request) Successful in 8m3s
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 14s
CI / PostgreSQL 16 integration (pull_request) Successful in 5m56s
CI / PostgreSQL 17 integration (pull_request) Successful in 6m5s
CI / Docker image (pull_request) Successful in 1m18s
8566072c9a
The owner's runner shares its CPU and disks with Gitea and the server's other
containers, so the 100k-frame bulk insert took 10-19 s against 15 s from one
run to the next. CHRONOS_TEST_TIME_FACTOR (default 1) stretches the timed
tests' budgets; CI and release set 3, the weekly performance gates keep them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Alby96 merged commit f2b58522b9 into main 2026-10-23 12:45:38 +02:00
Sign in to join this conversation.