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>
34 lines
1.7 KiB
C#
34 lines
1.7 KiB
C#
using Chronos.Testing;
|
|
using Chronos.Tools.Commands;
|
|
|
|
namespace Chronos.Tools.Tests;
|
|
|
|
/// <summary>Release notes from Conventional Commits (BRIEF §19.3), as release.yml renders them with a title.</summary>
|
|
public sealed class ChangelogCommandTests
|
|
{
|
|
[Test]
|
|
public void EntriesAreGroupedByTypeUnderTheTitle()
|
|
{
|
|
var notes = ChangelogCommand.Render(["abc1234\tfeat(editor): save the project as a .chronos file", "def5678\tfix: keep user data", "0a1b2c3\tchore: bump"], "Chronos 1.2.0");
|
|
Assert.Equal(
|
|
"# Chronos 1.2.0\n\n### Added\n- **editor**: save the project as a .chronos file (abc1234)\n\n### Fixed\n- keep user data (def5678)\n\n",
|
|
notes.ReplaceLineEndings("\n"));
|
|
}
|
|
|
|
[Test]
|
|
public void ATitledReleaseWithoutListedChangesSaysItIsAMaintenanceRelease()
|
|
{
|
|
string[] lines = ["abc1234\tchore: bump", "def5678\tci: cache", "0a1b2c3\ttest(setup): cover uninstall", "not a conventional subject"];
|
|
Assert.Equal("# Chronos 1.2.1\n\nMaintenance release.\n", ChangelogCommand.Render(lines, "Chronos 1.2.1").ReplaceLineEndings("\n"));
|
|
Assert.Equal("Maintenance release.\n", ChangelogCommand.Render(lines, null).ReplaceLineEndings("\n"));
|
|
Assert.Equal("Maintenance release.\n", ChangelogCommand.Render([], null).ReplaceLineEndings("\n"));
|
|
}
|
|
|
|
[Test]
|
|
public void ABreakingChangeOfAnUnlistedTypeIsStillWritten()
|
|
{
|
|
var notes = ChangelogCommand.Render(["abc1234\trefactor(core)!: rename the archive layout"], "Chronos 2.0.0").ReplaceLineEndings("\n");
|
|
Assert.Equal("# Chronos 2.0.0\n\n### Breaking changes\n- **core**: rename the archive layout (abc1234)\n\n", notes);
|
|
}
|
|
}
|