RepoJournal
Laravel

@laravel

PHP's most popular framework — Forge, Vapor, and a massive paying audience

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Thu 14 may
  13. Fri 15 may
  14. Sat 16 may
  15. Sun 17 may
  16. Tue 19 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

NIGHTWATCH LOCKS DOWN VAPOR SCHEDULING, MOAT HITS 1.0

By RepoJournal · Filed · About Laravel

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

References

  1. [1] v1.27.0 ↗ laravel/nightwatch
  2. [2] Handle `vapor:schedule` for sub-minute scheduling ↗ laravel/nightwatch
  3. [3] Resolve URI template variables when testing resources ↗ laravel/mcp
  4. [4] v1.0.0 ↗ laravel/moat
  5. [5] fix: old repositories not having security analysis laravel/moat
  6. [6] Fix Teams email verification redirect ↗ laravel/maestro

FAQ

What changed in Laravel on May 21, 2026?
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.
What should Laravel teams do about it?
Update Nightwatch to v1.27.0 if you're running Vapor with sub-minute schedules • Test MCP resource helpers with your existing URI templates after upgrading • Verify Moat v1.0.0 security analysis is enabled for your legacy repositories
Which Laravel repositories shipped on May 21, 2026?
laravel/nightwatch, laravel/mcp, laravel/moat, laravel/maestro

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.