Changelog

All notable changes to laravel-compose will be documented in this file.

• Drop Laravel 11 support
• Bump minimum illuminate/* requirements from ^11.0|^12.0|^13.0 to ^12.69|^13.30
• Add the package banner and icon

Laravel 11 stopped receiving security fixes on March 12, 2026. Three advisories published since then (GHSA-5vg9-5847-vvmq, GHSA-crmm-hgp2-wgrp and GHSA-jh5r-qr3c-85q8) affect every Laravel 11 release and were fixed only in Laravel 12 and 13. The new minimums, 12.69.0 and 13.30.0, are the first releases that include all three fixes.

If your app is still on Laravel 11, Composer keeps you on 1.0.3.

Full Changelog: 1.0.3...1.1.0

• Improve package setup

Full Changelog: 1.0.2...1.0.3

• The operator link is now named after the stack with dashes turned into underscores, so a stack named acme-search is linked at /home/ploi/containers/acme_search. That's the directory Ploi's panel creates for a container of that name. Until now the link landed next to it, where the panel never looks. A server that already has a dashed link keeps it as a leftover, so delete it once. Stacks that override linkPath() aren't affected.
• When a directory with files sits where the link should go, the deploy log and compose:doctor now print the sudo rm -rf that clears it. Ploi's panel leaves exactly that behind: a root-owned directory holding the panel's own docker-compose.yml, which the deploy user can't remove.
• The Ploi section of the hosting docs covers the setup in three steps: create the container in the panel with the stack's name, remove the directory the panel created, then deploy.

Full Changelog: 1.0.1...1.0.2

• Scaffolded healthchecks probe 127.0.0.1 instead of localhost. Inside a container localhost can resolve to ::1 first while the service listens on IPv4, and the check then fails with "connection refused" against a service that is fine. The compose file compose:make writes, the docs, and the Boost skill all follow suit.
• Two copy-and-paste recipes in the docs: Meilisearch for Laravel Scout, and a local Telegram Bot API server. Each has the compose file, the stack class, the config/services.php block, the .env keys, and the deploy lines, and both were brought up against a real daemon before publishing.

Full Changelog: 1.0.0...1.0.1

The first release. A Laravel app can now own the Docker Compose stacks it depends on and recreate them on every deploy with one command.

• A stack is a directory with a docker-compose.yml and, usually, a small Stack class beside it. app/Docker/* and Modules/*/Docker are found without configuration, and a directory with no class still counts.
• php artisan compose:redeploy writes the stack's env file from your config, refreshes the operator link, builds when asked, pulls, sweeps stale containers by name, and runs compose up. The order comes from production incidents, and the command is safe to run again.
• Env files are generated, quoted the way Compose reads them, written with 0600 permissions, and never shadowed by the app's own .env.
• compose:doctor checks the docker binary, the Compose plugin version, the daemon, every compose file, ${VAR} coverage, publishes on every interface, the link directory, and whether git ignores the env file.
• compose:status, compose:logs, and compose:down cover the day-to-day, and a StacksCheck for spatie/laravel-health watches the containers between deploys.
• Remote daemons through DOCKER_HOST or a docker context, four lifecycle events, and Compose::fake() with assertRedeployed() and friends for tests.
• Supports PHP 8.2 to 8.5 and Laravel 11 to 13.

Full Changelog: https://github.com/mozex/laravel-compose/commits/1.0.0