monooso/unobserve
Laravel package for temporarily disabling Eloquent model observers. Unobserve models to run saves, updates, or deletes without triggering observer events, then restore observation easily. Useful for imports, seeding, bulk operations, and other tasks where observer side effects should be skipped.
v7.0.0 is a platform-jump release, so treat the first step as an environment check rather than a feature tour.
composer require, verify:
php -v on your machine, in CI images, and in the production Dockerfile/base image.composer show laravel/framework — you must already be on Laravel 13. There is no graceful fallback; Composer will simply refuse to resolve.composer.json first, then the README. The release notes are release-engineering focused (tooling, CI, dev environment), not API focused, so the authoritative list of config keys, published assets, and service-provider bindings still lives in the README and config/ stub. Diff the published config against your existing one after upgrading.php artisan vendor:publish --provider=...), wire the facade/binding, and exercise the single most common path in a feature test before touching anything else../dev — local development now runs in Podman, with no host PHP or Composer required. That is the fastest way to reproduce issues against a known-good matrix.Pin deliberately — the support policy changed. v7 supports only the latest major of Laravel going forward, and older majors are no longer maintained. Two viable patterns:
// Laravel 13 app — track the major
"vendor/package": "^7.0"
// Laravel 11/12 app — freeze on the last tag that supported you
"vendor/package": "6.*"
Keep a short comment in composer.json or an ADR noting why the pin exists and which release was the last supported one. This is the single most important operational change in v7.
Upgrade as a dedicated, isolated change. Sequence it as: bump PHP image → bump Laravel → bump this package → run Pint → run the test suite. Doing the PHP/Laravel bump and the package bump in one commit makes bisecting a failure miserable.
Adopt Pint as the new house style. Linting switched to Laravel Pint, so formatting output will differ from whatever the package used before. Run vendor/bin/pint in a separate commit immediately after the upgrade so the reformat noise does not contaminate your actual upgrade diff.
Replace the removed quality gates with your own. Scrutinizer CI and the Git pre-push hook are both gone. If you relied on either:
vendor/bin/pint --test and your static analyser (PHPStan/Larastan) — this is now your responsibility, not upstream's.composer script; or better, enforce server-side with branch protection + required checks so it cannot be bypassed with --no-verify.Mirror the Podman dev environment in CI. ./dev gives you a reproducible container. Point CI at the same image/definition where practical — parity here eliminates a whole class of "works in ./dev, fails in Actions" bugs.
Guard the public surface in tests. On a major bump, write characterization tests around the behaviour you actually depend on (return shapes, exceptions, dispatched events, config keys) before upgrading. That converts an opaque breaking change into a concrete diff.
FROM php:x.y line, deploy hooks, and any locally pinned platform.php in composer.json — that last one is a common silent blocker.composer why-not vendor/package 7.0 is the fastest way to diagnose a failed Laravel 13 resolution. Usually it is a transitive illuminate/* constraint or a package stuck on Laravel 12.vendor:publish --force will overwrite local customisations, so publish to a temp path and compare manually.:z/:Z on bind mounts. If ./dev fails on first run, check mount labels before debugging the package.How can I help you explore Laravel packages today?