[Unreleased]
[1.3.0] - 2026-08-08
Breaking Changes
- Dropped Laravel 11 support: The
illuminate/supportconstraint narrows from^11.0|^12.0|^13.0to^12.0|^13.0, and theorchestra/testbenchdev constraint from^9.0|^10.0|^11.0to^10.0|^11.0. Every Laravel 11 release (v11.0.0 through v11.55.0) carries unpatched security advisories and 11.x is past its security-fix window, so Composer's advisory policy refuses to install any of them — Core can no longer install or test against Laravel 11 at all, which had been failing every Laravel 11 CI leg. Laravel 12 and 13 are unaffected. PHP 8.2 remains the minimum and now receives Laravel 12. Stay on Core 1.2.x if you must remain on Laravel 11, understanding that the framework itself is unpatched. SeeUPGRADE.md. MIN_LARAVEL_VERSIONcorrected to12.0.0:Constants::MIN_LARAVEL_VERSIONandDiagnostics\Checks\EnvironmentCheck::MIN_LARAVEL_VERSIONboth still read10.0.0, stale since 1.1 dropped Laravel 10, soartisanpack:diagnosereported unsupported framework versions as passing. Update any assertion on either constant.
Added
- Shared site resolution: Added
ArtisanPackUI\Core\Contracts\SiteResolver— the ecosystem's single answer to "which site is this code running for?". Every package that scopes records per site (analytics, bookings, and anything added later) now reads one contract, one container binding, and one configuration block, so a single request can no longer resolve to site 2 for one package while resolving to site 1 for another. The contract is keyed on the site identifier (int|string|null) rather than any package'sSitemodel, and takes noRequest, so it works unchanged inside console commands and queue workers. SiteContextservice: AddedArtisanPackUI\Core\MultiTenancy\SiteContext, the surface consumers actually talk to, shared across each request or queue job. Delegates to the bound resolver, applies theenabledflag, and addsforSite(),withoutSite(),setSiteId(),forget(), andflush()for pinning a site over a bounded stretch of work — restoring the previous context afterwards, including when the callback throws, and nesting safely. A pinned site wins over the resolver and applies even while automatic resolution is switched off, because pinning is an explicit instruction from the calling code. Scoped binding already clears a pin at the request or job boundary, so no Octane wiring is required;flush()is there for resetting deliberately mid-process. Reachable through the newArtisanPackUI\Core\Facades\ArtisanPackSitefacade (aliased asArtisanPackSite) and the newapCurrentSiteId()helper.- Shipped resolvers:
HookSiteResolver(the default — applies theap.cmsFramework.currentSite.resolvefilter, resolving to null where nothing answers, and raisingSiteResolutionExceptionwhereartisanpack-ui/hooksis not installed at all and there is therefore no filter to answer),NullSiteResolver(never puts a site in context), andChainSiteResolver(asks each configured resolver in turn and takes the first non-null answer). Nothing memoises: the resolver is asked on every call, because a worker looping over sites changes the answer within one process. artisanpack.core.multi_tenantconfiguration: One authoritative block —enabled(default false, so an unconfigured application stays single-tenant and every package leaves its queries unscoped) andresolvers(an ordered list ofSiteResolverclass names, assembled into the bound chain). A configured class that is missing or does not implement the contract raises the newSiteResolutionExceptionat bind time rather than being silently dropped, as does aresolversvalue that is not a list at all; a hook listener answering with an unusable value fails the same way. Coercing any of them to null would quietly unscope every query the resolution feeds. Only an explicit empty list switches resolution off.
Notes
- Nothing was removed and no existing behaviour changed; the site-resolution services are additive and inert until
artisanpack.core.multi_tenant.enabledis switched on. SiteResolverandSiteContextare bound withscoped()rather thansingleton(). Laravel forgets scoped instances between Octane requests and between queue jobs, which is what stops a pinned site outliving the job that pinned it, and what stops a request-dependent resolver freezing its first request's dependencies for the life of a worker. Both would otherwise scope later work to the wrong site silently.- The
multi_tenantdefaults are merged by the service provider, soARTISANPACK_MULTI_TENANT_ENABLEDtakes effect whether or not the application has publishedconfig/artisanpack.php. Core publishes rather than merges the rest of that stub, so without this an operator could switch tenancy on and have it silently ignored. artisanpack-ui/hooksis a suggestion rather than a requirement, and is only needed ifHookSiteResolverstays in the resolver list while tenancy is switched on.
[1.2.0] - 2026-05-23
Added
ArtisanPackServiceProviderbase class: Abstract base service provider that removes the boilerplate every sibling ArtisanPack UI package previously hand-rolled (config merging, command registration, view loading, route loading, container singletons). Child providers configure their behaviour declaratively through$configFile,$configKey,$configPublishTag,$commands,$singletons,$viewsPath,$viewsNamespace, and$routesPathproperties and only need to implement theregisterPackageBindings()hook for unique bindings. An optionalbootPackage()hook covers any boot-time logic that doesn't map to the standard hooks. Reduces a typical sibling provider to a handful of properties.- Unified configuration manager: Added
ArtisanPackUI\Core\Config\ConfigurationManagerfor reading, writing, merging, and validating the configuration of every installed ArtisanPack UI package. Hides the sharedartisanpack.<package>.<key>namespacing behind package-aware helpers (get,set,has,merge,validate,all,package,registerSchema,schema). Shipped alongsideConfigurationSchema(lightweighttype/required/inrule validation),ValidationResult(immutable outcome object), theArtisanPackConfigfacade, and theartisanpack_config()helper for one-off reads. Resolved as a singleton throughCoreServiceProvider. - Shared logging infrastructure: Added
ArtisanPackLogger,Logger, andLoggerFactoryunderArtisanPackUI\Core\Logging, plus theAuditLogCreatedevent and theArtisanPackLogfacade. Every ArtisanPack UI package can now route logs through a single channel with consistent[package]prefixes, structured context, and anaudit()method that records compliance-relevant actions and dispatches an event applications can listen for. Configurable viaartisanpack.core.logging.channel(falls back to Laravel's default channel) andartisanpack.core.logging.audit.enabled. - Blade directive registrar: Added
ArtisanPackUI\Core\View\BladeDirectiveRegistrarand the matchingartisanpack_blade()helper. Packages can now declare common directive patterns through intent-revealing methods (echo,escaped,conditional,wrap,livewireAction,facade) instead of hand-rolling PHP-string templates withBlade::directive(). Directive names are validated at registration so typos surface immediately rather than at template render. Resolved as a singleton throughCoreServiceProvider. ArtisanPackFacadebase class: Shared base for every ArtisanPack UI facade, providing consistent error messages when the underlying service is missing alongside helper methods for safely probing whether the service is available before resolving it. Subclasses overridegetFacadeAccessor()and may overridegetPackageName()so the missing-service exception names the package the consumer needs to install.- Constants + enums repository: Added
ArtisanPackUI\Core\Constants(package identifiers, configuration keys, default values, version baselines) and four enums underArtisanPackUI\Core\Enums—LogLevel,Package(withconfigKey()andshortName()helpers),Priority, andStatus. Single source of truth for primitives used across the ecosystem. - Base exception hierarchy: Added
ArtisanPackUI\Core\Exceptions\ArtisanPackExceptionplus five specialised subclasses —ConfigurationException,DependencyException,InstallationException,ServiceException,ValidationException. Catch the base class for any ArtisanPack UI error, or the specific subclass for a specific failure mode. - Testing utilities base classes: Added
ArtisanPackUI\Core\Testing\ArtisanPackTestCase(Orchestra Testbench base that registersCoreServiceProviderautomatically) plus three concerns —ArtisanPackAssertions(assertPackageInstalled,assertConfigEquals,assertCommandExists,assertFacadeWorks,assertHelperExists),InteractsWithConfiguration(withConfig,withPackageConfig), andMocksArtisanPackServices(swapArtisanPackService,mockArtisanPackService, plus dedicated shortcuts for the configuration manager, logger factory, and Blade directive registrar). Sibling packages can extend the base case and immediately reach for ecosystem-aware assertions and helpers. artisanpack:diagnosecommand: Runs the newDiagnosticRunneragainst five default checks —EnvironmentCheck(PHP / Laravel / Livewire versions + required PHP extensions),InstalledPackagesCheck,ConfigurationCheck(with auto-fix that invokesartisanpack:scaffold-config),ServiceBindingsCheck(verifiescoreanda11yaliases resolve to expected concretes), andArtisanCommandsCheck. Supports--json,--fix, and--package=<id>flags. Exits non-zero when any check reports an error.artisanpack:check-compatibilitycommand: Walks every installed ArtisanPack UI package's Composer requirements and reports inter-package, PHP version, Laravel version, and PHP extension constraint satisfaction via the newCompatibilityChecker. Supports--json,--strict(treat warnings as errors), and--package=<name>flags. Test overrides on the checker allow stubbing PHP version, Laravel version, loaded extensions, and the package list without touching the host environment.artisanpack:check-updatescommand: Readscomposer.lock, asks Packagist for the latest stable release of every installed ArtisanPack UI package, and produces a structured update report via the newUpdateCheckerandPackagistClient. Classifies each update as major / minor / patch, flags security-related releases by keyword scanning (security, vulnerability, cve-, xss, csrf, sql injection, remote code execution), and supports--json,--minor-only,--security-only, and--changelogflags. Packagist responses are cached forartisanpack.core.updates.cache_ttlseconds (default 3600), with cache entries refreshed on read so frequently-queried packages stay warm. Adopts Laravel 13'sCache::touch()behind amethod_exists()feature gate so custom cache repositories on Laravel 11/12 benefit too.artisanpack:make-packagecommand: Scaffolds a new ArtisanPack UI package from the standard blueprint —composer.jsonwired to the ecosystem's standard dev dependencies, a service provider that extendsArtisanPackServiceProvider, a facade, a config stub, Pest tests via Orchestra Testbench, and the conventional directory layout. Optional--with-livewire,--with-views,--with-routes,--with-migrations, and--with-commandsflags add additional structure. Validatesvendor/packagenaming format up front and protects existing non-empty directories ( opt-in via--force).- Laravel 13 support: Widened the
illuminate/supportconstraint from^11.0|^12.0to^11.0|^12.0|^13.0. Laravel 11 and 12 remain fully supported. The CI matrix now runs against Laravel 11, 12, and 13.
Changed
- Hardened CI: CI now runs on
release/**branches so v1.2 PRs are validated, workflow permissions tightened, and the release workflow now fails on Packagist errors rather than swallowing them silently.
Notes
- PHP 8.2+ remains the minimum requirement. Laravel 13 requires PHP 8.3+, so PHP 8.2 users continue to receive Laravel 11/12, while Laravel 13 is only selectable on PHP 8.3+ (enforced by Laravel's own PHP constraint).
- No public API was removed. Every Core 1.1 application continues to work after upgrading to 1.2 with no other changes required. Migration to the new services (
ArtisanPackServiceProvider,ConfigurationManager,ArtisanPackLog,ArtisanPackTestCase) is opt-in. SeeUPGRADE.mdfor the full migration guide.
[1.1.0] - 2026-01-09
Breaking Changes
-
Dropped Laravel 10.x support: The package now requires Laravel 11.0 or higher. Laravel 10.x is no longer supported due to PHP version compatibility requirements.
-
Removed accessibility helper functions: The following functions have been moved to the
artisanpack-ui/accessibilitypackage:a11y()a11yCSSVarBlackOrWhite()a11yGetContrastColor()a11yCheckContrastColor()generateAccessibleTextColor()
To continue using these functions, install the accessibility package:
composer require artisanpack-ui/accessibility
Changed
- Updated
illuminate/supportconstraint from^10.0|^11.0|^12.0to^11.0|^12.0 - Updated
laravel/promptsconstraint from^0.1|^0.2|^0.3to^0.3for stability (v0.3.0 introduced breaking changes to default-value handling)
Notes
- PHP 8.2+ is still required
- The GitLab CI pipeline uses PHP 8.4, which is fully compatible with Laravel 11 and 12
[1.0] - 2025-10-02
- Initial release of ArtisanPack UI Core package
- Added CoreServiceProvider for Laravel integration with singleton service registration
- Added artisanpack:scaffold-config command for unified configuration management
- Added Core facade for easy access to package functionality
- Added unified configuration system with artisanpack.php config file
- Added accessibility helper functions for color contrast and toast duration
- Added support for publishing and merging package configurations
- Added automatic config file scaffolding with --force option support
- Requires PHP 8.2+ and Laravel 10.0+

