v2.0.0
The first stable SqueHub v2 release establishes a PHP 8.2+ application framework with a modern HTTP stack, compiled Views, complete data and security foundations, background services, extensibility, portability, and bounded Agent/MCP integration.
Application foundation
- Application-owned services, dependency injection, providers, configuration, environment loading, diagnostics, logging, and request isolation.
- Modern routing with groups, named routes, middleware, model binding, route depth, trusted proxies, subdirectory hosting, and returnable response types.
- Validation, sessions, CSRF protection, browser forms, redirects, secure error handling, and request correlation.
- SqueHub Views with escaped output, layouts, sections, components, props, slots, includes, stacks, fragments, compiled artifacts, shared context, and returnable View responses.
Database, ORM, and application data
- Database connections, transactions, Schema, Migrations, Seeders, Factories, query building, pagination, and SQLite/MySQL portability work.
- Modern Models with guarded assignment, casts, scopes, soft deletion, eager loading, and complete relationship support.
- API resources, response and error contracts, CORS, API versioning, personal access tokens, OpenAPI export, and contract-driven client generation.
- Typed application data mapping and explicit validation boundaries for request-to-domain workflows.
Identity and security
- Authentication guards, authorization policies and RBAC, account security, password reset and verification tokens, sessions, and browser authentication flows.
- Personal access tokens, OAuth 2.1/OIDC integration direction, signed URLs, rate limiting, cryptography, trusted proxy handling, locks, and idempotency.
- Aggregate privacy-conscious diagnostics, safe exception boundaries, secret redaction, and production-safe debug behavior.
- Explicit application composition: authentication and account security remain independent from throttling, Mail, Notifications, and Queue policy.
Services and background work
- Cache and Redis integrations, Storage, Events, HTTP Client, Mail, Notifications, webhooks, and cryptography with application-owned resolution.
- Queue drivers and workers, retries, backoff, failed jobs, delayed work, queued Mail and Notifications, Scheduler persistence, and broadcasting/realtime foundations.
- Local and persistent drivers keep explicit capability and deployment boundaries; distributed guarantees are documented instead of implied.
Developer experience and ecosystem
- Packages and Kits with explicit discovery, installation, activation, provenance, reviewable changes, and large-application composition.
- Five focused generators, feature blueprints, SqueHub Setup, SqueHub Dev, testing helpers, reproducible request cases, Doctor, Health, and the read-only SqueHub Studio.
- Optional Vite, React, and Vue application profiles plus frontend authentication integration.
- Portable project bundles, deployment preflight, upgrade checks, recovery planning, and source-driven installation documentation.
- Bounded local Agent/MCP inspection and Change Plans without arbitrary shell, file, database, or network access.
Breaking changes from v1.x
- PHP 8.2 or newer is required, and application source uses canonical Project/ paths; App/Routes/ is no longer an application route source.
- New applications use Route::path(...) and the stable App\Plugins developer surface instead of relying on internal framework namespaces.
- Application Views live under Project/Views/ or activated Package namespaces; the former root Views/ fallback is discontinued.
- Seeder is the v2 data-seeding API. The v1 Dumper API and commands are retired, and reversible Seeder rollback must be explicit.
- Packages and Kits use reviewed installation and activation lifecycles; v1 automatic loading assumptions require migration review.
Release qualification
- The v2.0.0 tag passed the release CI suite on Ubuntu and Windows.
- The published Packagist package was verified through a public Composer create-project installation and fresh-application smoke checks.
- Existing v1 applications should follow the dedicated upgrade guide rather than treating v2 as a drop-in update.

