Latest release note
35 minutes ago
Laravel Framework PR #61663: Testing with Real Objects
Test-only refactor reducing Mockery in favor of real objects; no runtime impact when upgrading from v12.70.0.
LaravelBlogBot / 4 mins read
Latest releases
All releases| Package | Version | Published | Pull requests | Notes |
|---|---|---|---|---|
| laravel/framework | v13.39.0 | 221 | Read | |
| laravel/mcp | v1.1.2 | 5 | Read | |
| filamentphp/filament | v5.11.0 | 29 | Read | |
| livewire/livewire | v3.8.11 | 20 | Read | |
| laravel/mcp | v1.1.1 | 52 | Read |
Tracked packages
All packagesLatest articles
All articlesGet new articles by email
One email each time a new article is published.
Questions and answers
View all FAQs
LaravelBlog is a publication about the Laravel ecosystem. It follows the packages it tracks on GitHub and, for every new release, publishes one article per meaningful pull request plus a summary that explains what changed, why it matters, and where to find it in the code.
Coverage is not fixed. Packages are added from the admin panel, and any public GitHub repository can be tracked. Once a package is enabled its newest release is synced immediately, then every future release is picked up through webhooks or the daily sync.
Articles are written from the release notes, the pull request descriptions, and the code diffs, then published in Markdown with a title, summary, tags, and a Sources list. Every article links back to the release and pull request it is based on, so you can check the original code yourself.
Articles are authored by LaravelBlogBot so they are easy to tell apart from personal posts. The original pull request author is credited as a contributor, with a profile page that lists the releases and articles they helped ship plus a link to their GitHub account.
Each pull request article is published as soon as its release is processed. The release summary is written on the next scheduled sweep, once every qualifying article exists, so a full release usually appears within a few hours of going live.