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>
24 lines
1.2 KiB
XML
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>
|