iksaku/laravel-mass-update
Laravel Mass Update lets you update multiple Eloquent records with different values in a single SQL query. Instead of looping through models, pass an array of updates and let the package generate efficient CASE-based UPDATE statements for faster bulk edits.
Architecture fit. iksaku/laravel-mass-update is a thin Eloquent extension that adds bulk UPDATE execution modes to Laravel models, bypassing per-model event dispatch and row-by-row hydration for throughput. Architecturally it sits directly on top of the Eloquent builder and query grammar, so it inherits Laravel's connection/resolution model, transaction semantics, and database-driver behavior. 2.0.0 keeps that shape; the only public-surface change is the removal of Mode::massUpdateQuietly().
Integration feasibility. Composer-installable, no service provider configuration surface to speak of, no queue or cache dependencies. The 2.0.0 release adds a Laravel 13.x compatibility constraint, which is the primary reason to take it now — 1.0.9 consumers on Laravel 13 would otherwise be pinned to an unsupported framework version. The breaking change is narrow and mechanical to remediate: one static method removed from one enum.
Technical risk. Three items dominate:
| Risk | Severity | Notes |
|---|---|---|
Mode::massUpdateQuietly() removal |
Medium | Hard Error: Call to undefined method at runtime, not a deprecation. Only surfaces on the code path that calls it, so it will not fail at boot or in unrelated test suites. |
| Semantic equivalence of replacement | Medium | Laravel's Model::withoutTimestamps() disables updated_at touching for a callback scope. Teams must confirm their previous quiet-mode call had identical timestamp intent and that no other observers/listeners were being suppressed by the quiet path. |
| Package maintenance / bus factor | Medium | Single-maintainer community package. Acceptable for a bulk-write optimization, but it should not become load-bearing for data integrity without a fallback to raw DB::table()->update(). |
| Driver-specific SQL behavior | Low–Medium | Bulk update bypasses casts and mutators; behavior varies across MySQL/Postgres/SQLite. Pre-existing risk, unchanged in 2.0.0. |
Key questions for the engineering owner.
massUpdateQuietly() across our repositories, including vendor-published internal packages?updated_at mutation" guarantee and the "no model events fired" guarantee, or only the former? If any listener was implicitly suppressed before, behavior changes silently.Stack fit. Low-friction. The package is a pure-PHP, no-extension, no-daemon dependency that follows standard Laravel package conventions. It requires no infrastructure change, no environment variables, and no deployment topology adjustment. Fit is effectively "add to composer.json, run composer update."
Migration path. The upgrade is a two-step, single-PR affair for most services:
massUpdateQuietly. For each hit, replace with an explicit Model::withoutTimestamps(fn () => ...) wrapper around the existing mass-update call, preserving the surrounding query conditions verbatim. Where the prior call relied on event suppression beyond timestamps, use Model::withoutEvents() in combination rather than assuming equivalence.^2.0 and re-resolve against the target Laravel version. If the service must remain on an older Laravel, keep the ^1.0 constraint on a maintenance branch rather than backporting the 2.0.0 changes.Compatibility. Two axes to validate before merge: PHP version supported by the new Laravel 13 floor, and database driver coverage in CI. The second matters more than usual here — the package generates dialect-specific bulk UPDATE SQL, so a green test suite on SQLite does not certify Postgres or MySQL behavior.
Sequencing. Recommended order: (a) inventory call sites and confirm semantic intent; (b) land the withoutTimestamps rewrite against the current package version, so the behavioral change is isolated and testable on its own; (c) bump to ^2.0 and to Laravel 13 in a follow-up, ideally coordinated with the framework upgrade so there is a single verification pass rather than two. Do not combine the rewrite and the framework bump in one change set — a regression will be ambiguous to attribute.
Maintenance. Post-upgrade, the ongoing burden is close to zero: no configuration, no migrations, no scheduled tasks. The residual maintenance concern is upstream — a single-maintainer package means Laravel 14 compatibility will arrive on the maintainer's schedule, not ours. Budget a recurring review item ahead of each major framework upgrade, and keep the abstraction thin enough at call sites that replacing it with DB::table()->update() is a contained change.
Support. Support load should be negligible, but the failure mode is asymmetric: the removed method throws immediately and loudly, which is good for diagnosis. The dangerous support case is the opposite — a team that assumes withoutTimestamps suppresses all model events, ships it, and only discovers the gap when a downstream consumer notices missing webhook or index updates. Support documentation should state explicitly what the replacement does and does not cover.
Scaling. Unaffected by this release. Bulk UPDATE remains the scaling win it was in 1.0.9 — one statement instead of N — and the removal of the quiet-mode wrapper introduces no per-row overhead. If anything, the 2.0.0 path is marginally clearer to reason about under load because timestamp behavior is now governed by a documented framework primitive rather than a package-specific flag.
Failure modes. The realistic failure set is short: (1) missed call site → runtime Error on the specific update path; (2) partial semantic migration → silent behavioral drift in event consumers, with no error surfaced; (3) composer resolution conflict on a service still pinned to an older Laravel. Modes 1 and 3 are caught in CI or at boot; mode 2 is the one that requires deliberate verification, ideally a test asserting that downstream side effects are either still suppressed or intentionally reintroduced.
Ramp-up. Trivial. Any Laravel developer can read and modify call sites in under an hour; the concept is one enum choosing a write strategy. The only genuine learning requirement is understanding what Model::withoutTimestamps() scopes, which is a short framework doc read rather than package-specific knowledge — a net positive, since it retires a piece of proprietary API surface in favor of a documented Laravel primitive.
Recommendation: upgrade, with the rewrite landed separately from the framework bump. The 2.0.0 change set is small, the breaking change is mechanically remediable, and the Laravel 13 support is the substantive reason to move. The one item that should not be treated as routine is verifying that the withoutTimestamps substitution is behaviorally equivalent at every call site — that is where this release can bite quietly.
How can I help you explore Laravel packages today?