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
4 Commits
Author SHA1 Message Date
Alby96andClaude Opus 5.5 8566072c9a 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
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>
2026-10-23 12:19:36 +02:00
Alby96andClaude Opus 5.5 f4800fd86d 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
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>
2026-10-23 12:05:37 +02:00
Alby96andClaude Opus 5.5 7830fe46de 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
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>
2026-10-23 11:43:34 +02:00
Alby96andClaude Opus 5.5 5f27a86406 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
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>
2026-10-23 11:34:48 +02:00