v1.2.2
·
3 commits
to 1.x
since this release
Added
- Add
$databaseto theRefreshingDatabase,TablesDropped, andDatabaseRefreshedlifecycle events, and update their constructor argument order accordingly. - The
--explainoutput now displays both the active connection name and database name, making it easier to verify the exact database context before running the command.
Fixed
- Resolve the booted connection and database name from
--database, pass the database name toSchema::getTables()and the underlyingmigratecall, print both in--explainoutput, and dispatch lifecycle events with the resolved values so table discovery, drops, and migrations target the correct database.
Full Changelog: v1.2.1...v1.2.2