- How do I install tenantedlaravel/core in a Laravel application?
- Install it with Composer using composer require tenantedlaravel/core, then review the package's configuration and migration publishing steps for tenant resolution and database connections. Because the v1.2.0 notes do not publish a full install guide, confirm service provider registration and config keys against the repository README before wiring it into an existing app. Run your test suite after installation, especially tests that touch tenant-scoped models.
- Does tenantedlaravel/core support Laravel 13?
- Yes. v1.2.0 added Laravel 13 support in a semver-minor release, consistent with the package tracking Laravel's release cadence. The changelog does not state whether Laravel 13 was stable or pre-release at the time, so check the composer.json constraints before assuming production readiness. If you are on Laravel 11 or 12, confirm those versions are still declared in the same constraint set.
- How does tenantedlaravel/core resolve tenants by domain or subdomain?
- Tenant resolution is handled by identity resolvers that map the incoming request's domain or subdomain to a tenant before queries are scoped and connections are switched. v1.2.0 updates a deprecation warning for identity resolvers, so the resolution extension point is on a deprecation path. Audit any custom resolver you supply and watch deprecation output during your upgrade.
- Is upgrading to tenantedlaravel/core v1.2.0 a breaking change?
- No. The release is semver-minor with no declared breaking changes, and most of the change surface is test and tooling infrastructure rather than runtime behavior. The one runtime-adjacent item is the identity resolver deprecation warning. Treat it as a maintenance upgrade, but review deprecation notices as deadlines rather than noise.
- What is the identity resolver deprecation in tenantedlaravel/core v1.2.0?
- v1.2.0 updates a deprecation warning for identity resolvers, signaling that the identity resolution extension point is being phased out. The changelog does not include a removal timeline or migration guide, so ask the maintainer which resolver APIs are affected and which major version will remove them. If you ship a custom resolver, plan a migration now instead of waiting for the next breaking release.
- How do I scope Eloquent queries to the active tenant with tenantedlaravel/core?
- The package scopes Eloquent queries to the active tenant, so tenant context must be established before any tenant-owned model is queried. Keep resolution in the request lifecycle and be deliberate about code paths that run outside it, such as queued jobs, console commands, and tests. Write tests that assert cross-tenant reads fail, because scoping bugs are silent data leaks.
- Does tenantedlaravel/core switch database connections automatically?
- Yes. The package is designed to switch database connections automatically based on the active tenant, which is the core of its data isolation model. In production, validate tenant connection configuration, migration strategy, and rollback behavior in a staging environment. v1.2.0 does not change this runtime behavior, so isolate the package upgrade from any Laravel major upgrade.
- Can I use tenantedlaravel/core for a multi-tenant SaaS on a single codebase?
- Yes. It is positioned for SaaS applications that need domain or subdomain tenant resolution, Eloquent scoping, and automatic connection switching while keeping one codebase. The package's value is isolation without duplicating application code. Before committing, confirm the Laravel and PHP version matrix in composer.json against your stack.
- What testing and static analysis changes are in tenantedlaravel/core v1.2.0?
- v1.2.0 bumps PHPUnit, Testbench, and Larastan, removes the PHPStan baseline, and fixes outstanding PHPStan issues. The raised analysis bar can surface latent type errors in your own extension code that previously passed. Nightly CI runs were also added, which helps early detection of upstream breakage but can produce non-actionable red builds against unreleased framework versions.
- Should I upgrade tenantedlaravel/core before or after a Laravel major upgrade?
- Upgrade the package first on your current framework, then move Laravel underneath it. That sequencing isolates variables: you prove v1.2.0 is clean on Laravel 11 or 12 before testing Laravel 13. If you are already on Laravel 13, v1.2.0 is likely a prerequisite rather than an optional bump.