Repository navigation
1.0.0-rc.5
Pre-releaseThe last release candidate before 1.0.0. It rebuilds the execution engine around one path, cuts the API and the schema down to what 1.0 will freeze, and re-cuts the schema baseline.
Upgrading from rc.4: drop and reprovision every database, including one an earlier rc.5 build provisioned: the migrations table changed shape and nothing translates it. Acta.Relational and Acta.Runtime are gone (their code ships in Acta), each package has one namespace, and several types and views are renamed. The release notes list every change a consumer makes.
Highlights
- One execution path: a claim moves rows straight to Executing, one finalizer lands up to 128 completions in one call, and crash recovery runs on the workers' heartbeat. Execution profiles are gone.
- Drain against rc.4's best profile on the same machine: 66.4K jobs/s on PostgreSQL (was 29.0K), 25.3K on SQL Server (12.3K), 5.6K on SQLite (1.0K).
- Fixes found by the release reviews: a scope that throws while disposing no longer strands its job, control verbs inside a step decide the job, a non-retryable failure rolls a recurring job over instead of ending its schedule, and an uncaught exhausted step fails the job at once.
- A job's rows carry no foreign key to the job; purge and retention delete them with it.
Known gap: on Windows, SQLite picks up one job at a time in about 20 ms where rc.4 took 2: its busy wait sleeps a whole timer tick. The fix lands in 1.0.0.
Evidence: certified on ba12ef95, which the tagged commit follows with test fixes and docs only: the three standard gates, the PostgreSQL ensemble, and both million-job runs (1,005,000 jobs, 24 workers of 64 executors) on PostgreSQL and SQL Server passed, with worker kills in flight in every work shape. The benchmark round on the same commit is docs/reference/benchmark.md.
Release notes: https://github.com/acta-dotnet/acta/blob/v1.0.0-rc.5/docs/release-notes.md