Skip to content

ChronoStack 0.1.0-alpha.6

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 18 Nov 05:01
f13e901

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 sh

Windows (PowerShell):

$env:CHRONOSTACK_VERSION = "0.1.0-alpha.6"; irm https://github.com/Asmodeus14/ChronoStack/releases/download/v0.1.0-alpha.6/install.ps1 | iex

The 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, init and config; 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 starter chronostack.yml from 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. --print shows 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.ps1 fail after copying the binary. It now treats a missing PATH as empty.