Platform Release — v1.1.0
| Field | Value |
|---|---|
| Release tag | v1.1.0 |
| Release date | TBD — create GitHub Releases only after all three repos are merged and CI is green on main |
| Platform status | Production Ready / Stabilized |
| Scope | First official platform tag: foundation (auth, tenancy, RBAC, marketplace, billing, Leads/Tasks) + post-freeze stabilization (multi-provider email, hardening, notifications, Communication Templates, Larastan zero-debt, CI quality gates) |
This is the official first tagged platform release. Earlier docs referred to a logical freeze as v1.1.0-platform; no git tags existed. Per semantic versioning policy, the coordinated tag is clean v1.1.0 (no suffixes).
Do not create git tags or GitHub Releases until: Backend, Frontend, and Docs are merged to main, Quality Gates are green, and operators have reviewed this document.
Versioning
| Artifact | Version |
|---|---|
| Coordinated git tag (all three repos) | v1.1.0 |
SaaS-Frontend package.json | 1.1.0 |
SaaS-Docs package.json | 1.1.0 |
| SaaS-Backend | Tag-only (no Composer version field) |
Policy: clean Semantic Versioning only (vMAJOR.MINOR.PATCH). Do not use suffixes such as -platform, -stable, or -release.
Compatibility
| Component | Requirement |
|---|---|
| PHP | 8.3+ (CI: 8.4) |
| Laravel | 13.x |
| Node.js | 20+ (CI: latest LTS) |
| Frontend | React 19 SPA |
| Databases | MySQL/MariaDB or SQLite (tests) per environment |
| Queues | Redis recommended; workers must include emails,default |
| Realtime | Laravel Reverb (notifications) optional but recommended |
What’s included
Platform foundation
- Authentication (Central + Tenant), tenancy, Spatie RBAC +
module:{slug}licensing - Marketplace, billing ledger, payment gateways (Stripe + Manual / Creem path)
- Settings hierarchy, audit/activity logging, impersonation
- Reference modules: Leads, Tasks
- Architecture freeze — see Platform Freeze
Stabilization (this milestone)
- Multi-provider email —
EmailManager, SMTP/Postmark/Mailgun, Central + Tenant modes, logs, queue isolation - Production hardening — migrate-only modules/RBAC, auth≠RBAC, go-live runbooks
- Notifications — digests, prune, Reverb/Echo ops
- Communication Templates — platform module with data-migration registration
- Larastan level 5 — zero errors (typing/PHPDoc only; no behavior change)
- CI standardization — PR Quality Gates on Backend / Frontend / Docs; artifact publish on
mainonly
Breaking changes
Relative to pre-marketplace / plan-based licensing:
- Plans / Features / usage limits removed — licensing is module subscriptions only.
- Central SPA routes under
/central/*. - Entitlements API shape
{ core, modules }.
For installations already on the modular-marketplace line: no additional intended API breaks in this tag.
Upgrade / first production deploy
- Deploy Backend, Frontend, and Docs at tag
v1.1.0(same intent across repos). - Follow Upgrade Guide and Production Runbook.
- Complete Multi-Provider Email cutover (migrate,
email:migrate-tenant-mail-modes,queue:restart). - Confirm queue workers listen on
emails,default. - Do not run
db:seed/ catalog or permission seeders in production.
Testing / validation gate (pre-tag checklist)
| Gate | Target |
|---|---|
| Backend Larastan | 0 errors |
| Backend Pest | Full suite green |
| Backend Quality Gate + Laravel Tests | Green on main |
| Frontend Quality Gate | Green on main |
| Docs Quality Gate (VitePress + dead links) | Green on main |
| Staging smoke | Central + Tenant auth, mail test, one Leads/Tasks path |
Release execution order
- Merge Backend / Frontend / Docs stabilization PRs to
main - Confirm CI green on
mainfor all three - Configure branch protection (admin) — see Release Process
- Tag each repo
v1.1.0(Backend → Frontend → Docs) - Create GitHub Releases linking this page
- Deploy and verify per runbook
Known limitations
- Contacts / Companies / Calendar / Activities still planned (CRM roadmap)
- Lead convert remains status-oriented until Contacts ships
- Some Central Billing UI surfaces remain ledger/ops oriented