Files
Chronos/Chronos.slnx
T
Alby96andClaude Opus 5.5 f2b58522b9
CI / Build and test (push) Successful in 8m14s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 7s
Release / Build, test and publish (push) Successful in 13m19s
CI / PostgreSQL 16 integration (push) Successful in 4m49s
CI / PostgreSQL 17 integration (push) Successful in 5m28s
CI / Docker image (push) Successful in 53s
Release / Server image (push) Failing after 10s
refactor!: rename Titano to Chronos and move CI and releases to Gitea (#6)
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>
2026-10-23 12:45:18 +02:00

24 lines
1.2 KiB
XML

<Solution>
<Folder Name="/src/">
<Project Path="src/Chronos.Core/Chronos.Core.csproj" />
<Project Path="src/Chronos.Core.Windows/Chronos.Core.Windows.csproj" />
<Project Path="src/Chronos.Data/Chronos.Data.csproj" />
<Project Path="src/Chronos.Protocol/Chronos.Protocol.csproj" />
<Project Path="src/Chronos.Server/Chronos.Server.csproj" />
<Project Path="src/Chronos.Ui/Chronos.Ui.csproj" />
<Project Path="src/Chronos.App/Chronos.App.csproj" />
<Project Path="src/Chronos.Uploader/Chronos.Uploader.csproj" />
<Project Path="src/Chronos.Setup/Chronos.Setup.csproj" />
<Project Path="src/Chronos.Tools/Chronos.Tools.csproj" />
</Folder>
<Folder Name="/tests/">
<Project Path="tests/Chronos.Testing/Chronos.Testing.csproj" />
<Project Path="tests/Chronos.Core.Tests/Chronos.Core.Tests.csproj" />
<Project Path="tests/Chronos.Core.Windows.Tests/Chronos.Core.Windows.Tests.csproj" />
<Project Path="tests/Chronos.Data.Tests/Chronos.Data.Tests.csproj" />
<Project Path="tests/Chronos.Server.Tests/Chronos.Server.Tests.csproj" />
<Project Path="tests/Chronos.App.Tests/Chronos.App.Tests.csproj" />
<Project Path="tests/Chronos.Tools.Tests/Chronos.Tools.Tests.csproj" />
</Folder>
</Solution>