Current SqueHub versionv2.0.0
Release history

Changelogs

Explore the complete SqueHub v2.0.0 release record and the verified v1.x history from the initial release through v1.2.2.

Current stable release

SqueHub v2.0.0

Current stable

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.

TERMINAL
composer create-project
squehub/squehub my-app "^2.0"

Released

Complete release record

From the first release to today.

The v2 release is the current framework generation. The v1.x entries remain here as a historical record for applications that still use the archived APIs.

SqueHub v2

v2.0.0

Current stable

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.
Legacy generationSqueHub v1.x

Maintained here for historical and migration reference.

SqueHub v1.x

v1.2.2

Final v1 release

A portability and configuration-hardening maintenance release for the final v1.x line.

Fixed and improved

  • Corrected Linux case-sensitive generator loading by canonicalizing the CLI Make directory name.
  • Restructured controller, Dumper, middleware, migration, and model generator files for cross-platform CLI compatibility.
  • Removed the tracked .env file and strengthened ignore rules so private environment configuration is not published with application source.
  • Improved View cache-directory creation and handling.
  • Updated framework version metadata to 1.2.2 and included minor maintenance fixes.
SqueHub v1.x

v1.2.1

Legacy

A View-engine refinement release focused on inherited data, nested templates, and safer internal variable handling.

Views and templates

  • Allowed @extends and @include to inherit defined View variables when no explicit data array is supplied.
  • Optimized the Blade-like compiler and improved variable scope across nested templates.
  • Automatically passed shared variables to layouts and partials while retaining explicit overrides.
  • Excluded internal rendering variables from inheritance to reduce collision and memory-safety risks.
  • Fixed variable collisions in recursive nested @include calls.
  • Updated the v1 Views guide to document optional data passing.
SqueHub v1.x

v1.2.0

Legacy

Expanded v1 application modularity through Package loading, project Views, middleware, utilities, and richer template composition.

Packages and application structure

  • Automatically loaded Package routes, Views, controllers, Models, and helper/utility files from project/Packages.
  • Added Package middleware registration for modular request filtering and authentication integration.
  • Loaded project/Utils and Package Utils files globally for application helpers.
  • Expanded View lookup to both the framework root views directory and project/Views.

Views and reliability

  • Added explicit data arrays to @include and @extends for reusable, dynamic templates.
  • Improved debug output, exception handling, logging, and graceful fallbacks.
  • Fixed minor issues across View rendering and route binding.
SqueHub v1.x

v1.1.0

Legacy

Improved template execution, dependency compatibility, helper access, and contributor documentation.

Changed

  • Improved the template parser with faster eval-based handling.
  • Upgraded Illuminate dependencies to the 10.x line and addressed PHP 8.1+ deprecation warnings.
  • Made SqueHub helper functions globally available without namespace imports.
  • Removed the deprecated View::inject() helper.
  • Updated contributor documentation for framework and Package contributors.
  • Fixed minor View-rendering and route-binding issues.
SqueHub v1.x

v1.0.0

Initial release

The first public SqueHub framework release introduced the original lightweight MVC application model.

Initial capabilities

  • Introduced routing, controllers, middleware, CSRF protection, a Blade-like View layer, basic ORM support, and the built-in CLI.
  • Established the original MVC structure plus custom components and Package support.
Upgrading an existing application

v2 is a new framework generation.

Move a v1 application in a separate branch or copy, preserve its data and persistent files, and review each application boundary before switching traffic. Do not treat v2 as a drop-in dependency update.