Upgrading

General upgrade steps

Every Crontinel upgrade follows the same sequence:

composer update crontinel/laravel
php artisan migrate
php artisan config:clear
php artisan cache:clear
php artisan crontinel:check

Update the package via Composer.
Run migrations. New releases may add or modify database tables. The package uses its own migration files, so this is safe to run alongside your app migrations.
Clear config and cache. This ensures Laravel picks up any new config defaults or service provider changes.
Run the health check. Confirms your database tables are current, the API key is valid (if configured), and monitors are responding.

When a new version introduces config options, your existing config/crontinel.php won’t include them automatically. You have two options:

php artisan vendor:publish --tag=crontinel-config

This will prompt before overwriting your file. Decline the overwrite, then diff the new defaults against your current config.

Check the version-specific notes below and add the new keys manually. This is faster when only a few options changed.

Released: 2026-11-02

Outcome::output(): Set the text sent as a run’s output, cut to 10,000 characters. A failure keeps the exception message and adds this text.
CRONTINEL_CAPTURE_OUTPUT=true: Opt-in. Sends the last 10,000 characters of the task’s sendOutputTo() / appendOutputTo() / storeOutput() file. Off by default because output may hold sensitive data. Add 'capture_output' => env('CRONTINEL_CAPTURE_OUTPUT', false), under cron in a published config.
Agent metric names: tokens_used, cost_usd and tool_calls through Outcome::metric().

Pin with composer require crontinel/laravel:^0.9. See Run output.

Released: 2026-10-09

Outcome::metric() / Outcome::timestamp(): Record a business count or artifact time on the terminal receipt. Exit 0 still means the process finished. Zero is sent when you record it. A run that records nothing omits outcomes.
Stable job_name: Schedule::name() (plus expression and a single environment) travels with the receipt so a renamed command or Schedule::call closure can keep a rule.
php artisan crontinel:schedule: Names the Laravel schedule in Crontinel and can set the processed_records minimum. From v0.9.2 it also turns on missed-run alerts; run it again after upgrading.

Pin with composer require crontinel/laravel:^0.8. Dogfood evidence for the Packagist artifact lives in the workspace planning notes.

Released: April 8, 2026

SaaS reporting: When CRONTINEL_API_KEY is set, the package automatically sends a status ping to app.crontinel.com every minute via the crontinel:report scheduled command. Individual cron run events are also pushed after each task completes or fails.
Webhook alert channel: A new webhook alert channel sends structured JSON POST payloads (both fire and resolve events) to any URL you specify.
crontinel:report command: Manually trigger a SaaS status ping at any time.
crontinel:prune command: Delete old cron_runs records beyond the retention window. Accepts --days=N to override the configured value.

Cron late detection: Fixed incorrect isLate calculation that used Carbon::now()->next(closure). The check now uses CronExpression::getPreviousRunDate() to correctly determine whether a cron missed its scheduled window. If you previously saw false late alerts, this release resolves the issue.

None. This is a backward-compatible minor release.

Add the following to your config/crontinel.php if they are missing:

// Inside the 'alerts' array, add the webhook channel:
'webhook' => [
    'url' => env('CRONTINEL_WEBHOOK_URL'),
],

Variable	Purpose
`CRONTINEL_API_KEY`	SaaS API key for status reporting to app.crontinel.com
`CRONTINEL_API_URL`	SaaS endpoint (defaults to `https://app.crontinel.com`)
`CRONTINEL_WEBHOOK_URL`	Webhook endpoint for the `webhook` alert channel

To use the webhook channel, update your .env:

CRONTINEL_ALERT_CHANNEL=webhook
CRONTINEL_WEBHOOK_URL=https://your-endpoint.example.com/webhook

This release includes a migration. Run php artisan migrate after updating.

Released: April 5, 2026

This is the first stable release. No upgrade path needed; install from scratch using the Quick Start guide.

Horizon monitor (supervisor status, paused state, failed jobs per minute)
Queue monitor (depth, failed count, oldest job age for Redis and database drivers)
Cron monitor (automatic run recording via scheduler events)
Dashboard at /crontinel with dark theme and 30-second auto-refresh
crontinel:check CLI command with --json and --no-alerts flags
crontinel:install CLI command
Alert channels: Slack webhook and email, with 5-minute deduplication
JSON API at /crontinel/api/status