# Changelog **Package:** Laravel Worktree | **Version:** 1 | **URL:** https://mozex.dev/docs/laravel-worktree/v1/changelog --- All notable changes to `laravel-worktree` will be documented in this file. ## 1.6.0 - 2026-08-20 ### What's Changed * `database.phpunit_files` now patches every listed file that exists instead of only the first, and reads each file for the connection its own suite runs on. A project that runs a second suite from a second config, browser tests beside the main suite for example, lists both and each file gets the worktree's own test database name plus the `skip-worktree` bit. A file left off the list keeps the name the main checkout put there, so from inside a worktree that suite runs against the main checkout's test database, and nothing shows it: the suite is green, and the parallel-test databases it spawns sit outside what teardown drops. Teardown now drops across every connection those files pin, collapsing to a single drop when they agree, which is the usual case. * Added a `suggest` entry for `mozex/laravel-test-lanes`, whose lane databases `worktree:teardown` already reaps. **Full Changelog**: [1.5.0...1.6.0](https://github.com/mozex/laravel-worktree/compare/1.5.0...1.6.0) ## 1.5.0 - 2026-08-01 ### What's Changed * `worktree:teardown` now also drops the `{name}_test_{token}` databases parallel test runs derived from the worktree's databases, covering both paratest worker indexes and mozex/laravel-test-lanes lanes, so they no longer outlive the worktree. Only token-shaped suffixes (digits, or `lane` plus digits) qualify, which keeps a sibling worktree whose slug happens to extend the prefix untouched, and every discovered name passes the same main-database guard as the worktree's own databases. * Database drops are now keyed by server and name together, so two connections that provision the same database name on different servers both get their database dropped instead of one being quietly left behind. **Full Changelog**: [1.4.0...1.5.0](https://github.com/mozex/laravel-worktree/compare/1.4.0...1.5.0) ## 1.4.0 - 2026-07-20 ### What's Changed * Added an `env.replace` option that rewrites env values per worktree, such as a Redis or cache prefix. Each entry maps a key to a template built from the worktree's tokens and the key's current value, so the value carries the worktree's slug without a hardcoded handler for it. The rewrites apply to the copied `.env` and to every file in `env.copy`. * Added isolation for more than one database connection. List each connection under `database.connections`, and every worktree gets its own database on all of them, application and test, created on setup and dropped on teardown. Teardown guards each connection against its own database in the main `.env`. This replaces the single `database.name` and `database.test` settings. * Added an opt-in `dependencies` option that copies `vendor` and `node_modules` from the main repository instead of installing them, as long as the worktree's lock file matches. A warm copy of `vendor` ran about five times faster than `composer install` in testing. A branch that changed its lock installs normally, and `npm ci` now lives in this block rather than in `steps`. * A published config file is now merged with the package defaults one level deeper, so a config written before one of these options existed still receives it instead of losing the whole block. **Full Changelog**: [1.3.1...1.4.0](https://github.com/mozex/laravel-worktree/compare/1.3.1...1.4.0) ## 1.3.1 - 2026-07-16 ### What's Changed * The config defaults for `herd` and `database.migrate` are now plain strings instead of enum values. A published config kept the enum imports, and on a production deploy without dev dependencies those classes do not exist, so loading the configuration failed. **Full Changelog**: [1.3.0...1.3.1](https://github.com/mozex/laravel-worktree/compare/1.3.0...1.3.1) ## 1.3.0 - 2026-07-16 ### What's Changed * Added `worktree:list`, which shows every worktree with its branch, path, URL, and database. * Added an `env.copy` option that copies extra gitignored env files (`.env.testing` by default) into the worktree, with the host rewritten. * `worktree:setup` now resumes a worktree that already exists for the branch, so a failed provisioning step no longer forces a full teardown. * Worktree sites are linked in Herd before being secured. A worktree in a nested path such as `.worktrees` used to get a certificate for a site that never answered. * Every command now refuses to run from inside a linked worktree and points back at the main repository. * Fixed the test database being created and dropped on the app's default connection instead of the one `phpunit.xml` pins. A project that develops on SQLite and tests against MySQL used to fail setup outright. * Teardown refuses `--pr` and `--into` on a detached worktree, database names are capped at the server's identifier limit, failed commands report their stdout when stderr is empty, and `export KEY=value` env lines are recognized when isolating child processes. **Full Changelog**: [1.2.1...1.3.0](https://github.com/mozex/laravel-worktree/compare/1.2.1...1.3.0) ## 1.2.1 - 2026-07-16 ### What's Changed * Depend on the split `illuminate/*` components (console, contracts, filesystem, process, support) instead of `laravel/framework`. This keeps the package clear of the framework's security advisories while still supporting Laravel 11, 12, and 13. **Full Changelog**: [1.2.0...1.2.1](https://github.com/mozex/laravel-worktree/compare/1.2.0...1.2.1) ## 1.2.0 - 2026-07-16 ### What's Changed * The default Node step is now `npm ci` instead of `npm install`. Laravel's `package.json` ships without a `name`, so `npm install` rewrote the tracked `package-lock.json` with the worktree's own directory name; `npm ci` installs from the lockfile and leaves it untouched. * Reworked the Warp tab configs with tab titles and clearer names (Create, Resume, Finish). **Full Changelog**: [1.1.0...1.2.0](https://github.com/mozex/laravel-worktree/compare/1.1.0...1.2.0) ## 1.1.0 - 2026-07-16 ### What's Changed * Fixed a blank or quoted branch name creating a `repo-''` worktree. A blank branch now auto-generates a name, as the docs always said it would. * Added `--print-path` to `worktree:setup`, which prints only the resolved worktree path so a shell button can `cd` straight into the new worktree. * Fixed the Warp terminal config so leaving the branch blank works and drops you into the worktree, generated name and all. **Full Changelog**: [1.0.0...1.1.0](https://github.com/mozex/laravel-worktree/compare/1.0.0...1.1.0) ## 1.0.0 - 2026-07-16 ### What's Changed * Initial Release **Full Changelog**: https://github.com/mozex/laravel-worktree/commits/1.0.0 --- ## Table of Contents - [Quick Start](https://mozex.dev/docs/laravel-worktree/v1) - [AI Integration](https://mozex.dev/docs/laravel-worktree/v1/ai-integration) - [Support Us](https://mozex.dev/docs/laravel-worktree/v1/support-us) - [Requirements](https://mozex.dev/docs/laravel-worktree/v1/requirements) - [Changelog](https://mozex.dev/docs/laravel-worktree/v1/changelog) - [Contributing](https://mozex.dev/docs/laravel-worktree/v1/contributing) - [Questions & Issues](https://mozex.dev/docs/laravel-worktree/v1/questions-and-issues) - [About Mozex](https://mozex.dev/docs/laravel-worktree/v1/about)