Repository navigation
Releases
ChronoStack 0.1.0-alpha.6
ChronoStack 0.1.0-alpha.6 (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.6/install.sh | CHRONOSTACK_VERSION=0.1.0-alpha.6 shWindows (PowerShell):
$env:CHRONOSTACK_VERSION = "0.1.0-alpha.6"; irm https://github.com/Asmodeus14/ChronoStack/releases/download/v0.1.0-alpha.6/install.ps1 | iexThe CLI pulls the matching controller image (ghcr.io/asmodeus14/chronostack-clockd:0.1.0-alpha.6, 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; an install test on Apple-silicon and Intel macOS runners (installer, native binary,
initandconfig; no Docker engine). - Manual checklist (not automated):
- macOS on Apple silicon with a running Docker engine (Docker Desktop or OrbStack): not yet tested, see issue #5
- Windows 11 + Docker Desktop (WSL2): tested by the maintainers during development
Changes
Added
chronostack init: writes a starterchronostack.ymlfrom your compose file. It detects Postgres (and pg_cron), Redis, Sidekiq, Celery (beat, workers, embedded-B, django-celery-beat) and Node workers. It adds a Sidekiq barrier when there's a Redis service, and commented suggestions for BullMQ, Celery and triggers. It warns when Celery beat lacks--max-interval 1.--printshows the file without writing it; an existing file is only replaced with--force. The generated file is validated before it's written.
Fixed
- Windows installer: an account with no user-level PATH made
install.ps1fail after copying the binary. It now treats a missing PATH as empty.
ChronoStack 0.1.0-alpha.5
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".
ChronoStack 0.1.0-alpha.4
ChronoStack 0.1.0-alpha.4 (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.4/install.sh | CHRONOSTACK_VERSION=0.1.0-alpha.4 shWindows (PowerShell):
$env:CHRONOSTACK_VERSION = "0.1.0-alpha.4"; irm https://github.com/Asmodeus14/ChronoStack/releases/download/v0.1.0-alpha.4/install.ps1 | iexThe CLI pulls the matching controller image (ghcr.io/asmodeus14/chronostack-clockd:0.1.0-alpha.4, 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; 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 (Docker Desktop or OrbStack): not yet tested, see issue #5
- Windows 11 + Docker Desktop (WSL2): tested by the maintainers during development
Changes
Added
- Scenarios:
advance: { to: "${var}" }accepts a value saved by an earlier step, so a test can advance to a time read from the data (for example a subscription's period end). Found while testing Polar.
Fixed
- App containers that set
POSTGRES_PASSWORDorPOSTGRES_USER(to connect to a database) no longer fail every probe, andup --wait, with "unavailable". When the Postgres probe gets no answer, ChronoStack checks the container's own clock instead. Images named pgvector, postgis or timescale are also recognised as Postgres servers. Found while testing Chatwoot.
Documentation
- Guide: BullMQ can take up to about 10 s to pick up a due job, and a slow job holds up a one-at-a-time queue in real time; a barrier that counts due delayed jobs, with an example. Found while testing Twenty.
- Guide: sidekiq-cron skips a run it notices more than 60 s late; how to land steps for it. Found while testing Chatwoot.
ChronoStack 0.1.0-alpha.3
ChronoStack 0.1.0-alpha.3 (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.3/install.sh | CHRONOSTACK_VERSION=0.1.0-alpha.3 shWindows (PowerShell):
$env:CHRONOSTACK_VERSION = "0.1.0-alpha.3"; irm https://github.com/Asmodeus14/ChronoStack/releases/download/v0.1.0-alpha.3/install.ps1 | iexThe CLI pulls the matching controller image (ghcr.io/asmodeus14/chronostack-clockd:0.1.0-alpha.3, 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; 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 (Docker Desktop or OrbStack): not yet tested, see issue #5
- Windows 11 + Docker Desktop (WSL2): tested by the maintainers during development
Changes
Fixed
- One-shot containers that exit with code 0, such as a migrator, no longer fail every
advance, scenario anddoctorrun with "unavailable". They are reported ascompleted. A container that exited with an error still fails. Found while testing Plane's self-hosted stack.
Documentation
- Guide: schedulers that fire on their own (Celery beat) run a missed job when the clock lands, not at the job's own time, and how to land steps for exact-time tests. Also: don't mount your own files at
/chronostack.
ChronoStack 0.1.0-alpha.2
ChronoStack 0.1.0-alpha.2 (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.2/install.sh | CHRONOSTACK_VERSION=0.1.0-alpha.2 shWindows (PowerShell):
$env:CHRONOSTACK_VERSION = "0.1.0-alpha.2"; irm https://github.com/Asmodeus14/ChronoStack/releases/download/v0.1.0-alpha.2/install.ps1 | iexThe CLI pulls the matching controller image (ghcr.io/asmodeus14/chronostack-clockd:0.1.0-alpha.2, 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; 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 (Docker Desktop or OrbStack): not yet tested, see issue #5
- Windows 11 + Docker Desktop (WSL2): tested by the maintainers during development
Changes
The first published pre-release. It includes everything listed under 0.1.0-alpha.1, which was built but not published.
Added
chronostack update [--check] [--version X] [--pre] [--force]: updates the CLI from GitHub Releases. It verifiesSHA256SUMSand replaces the running binary (Windows included), with no admin rights.- Installers put
chronostackon PATH.install.ps1also updates the current PowerShell session, so it works immediately.install.shadds one marked line to the shell's startup file (zsh, bash, fish or~/.profile) and prints the command for the current terminal.CHRONOSTACK_NO_MODIFY_PATH=1opts out. - GitHub Action (
action.yml), MCP bundles andserver.jsonfor the MCP Registry,docs/GUIDE.md, demo GIF, launch drafts.