$ the-wire · showcase
NIGHTWATCH LOCKS DOWN VAPOR SCHEDULING, MOAT HITS 1.0
By RepoJournal · Filed · About Laravel · Composed from the cited sources · methodology
Nightwatch v1.27.0 now tracks sub-minute Vapor schedules correctly, while Moat ships its first stable release with security analysis fixes for legacy repositories.
Nightwatch v1.27.0 landed with a critical fix for Vapor users: the test helper now properly handles sub-minute scheduling by listening to the `vapor:schedule` command and tracking each scheduled task as a separate entrypoint [1] [2]. The release also standardizes naming conventions, adds new test assertions, and fixes Laravel 13 serialization issues [1]. Over in MCP, the resource testing helper now resolves URI template variables before dispatching requests, so templates like `file://summary/{id}` properly expand with provided arguments [3]. Moat shipped v1.0.0 with a critical fix for old repositories not having security analysis enabled by default [4] [5], marking the first stable release after months of development. Maestro fixed a 404 that appeared after email verification in Teams variants by redirecting to the team-prefixed dashboard instead of the default `/dashboard` route [6].
Action items
- → Update Nightwatch to v1.27.0 if you're running Vapor with sub-minute schedules laravel/nightwatch [plan]
- → Test MCP resource helpers with your existing URI templates after upgrading laravel/mcp [monitor]
- → Verify Moat v1.0.0 security analysis is enabled for your legacy repositories laravel/moat [plan]
- → Rebuild Maestro Teams variants to pick up email verification redirect fix laravel/maestro [plan]
References
- [1] v1.27.0 ↗ laravel/nightwatch
- [2] Handle `vapor:schedule` for sub-minute scheduling ↗ laravel/nightwatch
- [3] Resolve URI template variables when testing resources ↗ laravel/mcp
- [4] v1.0.0 ↗ laravel/moat
- [5] fix: old repositories not having security analysis ↗ laravel/moat
- [6] Fix Teams email verification redirect ↗ laravel/maestro
