After three weeks of internal production validation without surfacing new bugs, scabarcas/laravel-permissions-redis ships its first stable 4.x release today. The codebase is identical to v4.0.0-beta.2 . What changed is the commitment. Why "no code changes" is the point Stable doesn't mean "we added features." Stable means "we stop changing this." For three weeks I ran the beta in my own production workloads, expecting to find something — an edge case, a race condition, a missed invalidation. Nothing surfaced. The Redis contract test suite stayed green, the in-memory test fake matched the real Redis implementation, and the resolver behaved consistently across queue workers, Octane lifecycles, and multi-user-model setups. When a beta runs long enough to stop producing new bug reports, the right thing is to stop labeling it beta. Three weeks felt like enough. What you get if you're coming from v3 or earlier The 4.x line has been collecting features since late March.…