Repository navigation
ChronoStack 0.1.0-alpha.5
Pre-release
Pre-release
·
8 commits
to main
since this release
ChronoStack 0.1.0-alpha.5 (pre-release): Stripe Test Clocks for your Docker Compose stack.
Install
Linux / macOS:
curl -fsSL https://github.com/Asmodeus14/ChronoStack/releases/download/v0.1.0-alpha.5/install.sh | CHRONOSTACK_VERSION=0.1.0-alpha.5 shWindows (PowerShell):
$env:CHRONOSTACK_VERSION = "0.1.0-alpha.5"; irm https://github.com/Asmodeus14/ChronoStack/releases/download/v0.1.0-alpha.5/install.ps1 | iexThe CLI pulls the matching controller image (ghcr.io/asmodeus14/chronostack-clockd:0.1.0-alpha.5, pinned by digest) on first chronostack up. Every file below is listed in SHA256SUMS; the SBOM is SPDX JSON.
Verified for this release
- Automated: unit tests on Linux, Windows and macOS; end-to-end tests (M1–M4) on Linux x86_64 and arm64; M1 and M2 with the native macOS CLI on an Intel macOS runner (Docker in a Linux VM); a smoke test that installs from these files on fresh Linux x86_64 and arm64 runners and runs the demo scenario.
- Manual checklist (not automated):
- macOS on Apple silicon (Docker Desktop or OrbStack): not yet tested, see issue #5
- Windows 11 + Docker Desktop (WSL2): tested by the maintainers during development
Changes
Added
- Built-in queue barriers:
bullmq: { service, queues, prefix }(also works with Bull) andsidekiq: { service, namespace }. They wait until nothing is queued, running, or delayed and already due, read with Redis's own (virtual) clock. The Sidekiq barrier also waits for a Sidekiq heartbeat after the queues look empty, because Sidekiq only reports running jobs on its heartbeat. settleon any barrier: wait that long at each stop before the first check, for schedulers that enqueue work on their next poll (sidekiq-cron, Clockwork).
Changed
- macOS: the native macOS CLI is tested in CI (nightly), against Docker in a Linux VM (Colima) on GitHub's Intel macOS runners: the M1 and M2 end-to-end suites pass. Apple-silicon Macs are still untested (#5).
advancechecks the barriers before its first jump too, so no job is running when the clock moves. A job in flight during a jump could see its Redis lock expire with the jump; BullMQ then ran it a second time as "stalled".