Release, Support & Security

SeviaFlow 0.1.x-dev is pre-release software. This page records the current technical distribution contract and does not grant a license or promise production support.

Changelog

0.1.x-dev — release contract preparation

Documented Core headless, Core + UI, API headless and full-runtime package profiles.
Documented migration, asset publishing, basic Resource setup and non-destructive package removal.
Aligned package descriptions with the current Composer manifests: API and Framework are part of the free edition.
Adopted MIT for all five free packages, corrected installer failure codes and separated the free Northstar profile from optional modules.
Expanded CI to supported PHP, Laravel and Livewire combinations, plus free and full Northstar integration suites.

Beta compatibility

CI covers PHP 8.2 / Laravel 12 and PHP 8.3 / Laravel 12 and 13. UI covers Livewire 3 and 4. Laravel 11 is no longer supported in this beta. SQLite is used for package tests and MariaDB 10.11 for Northstar; PostgreSQL awaits verification.

Known limitations

Core, UI, API, Framework and DevTools use MIT. Other repositories retain their own license terms.
The five free packages do not require a separate licensing package at runtime.
Declared PHP, Illuminate, Livewire and database ranges are compatibility declarations. Only the versions recorded in the support matrix are verified.
Versioned release artifacts, clean-install and upgrade proofs belong to D02 and are not implied by this documentation change.

Support scope

Until the owner publishes a support policy, no response time, supported-version window or production SLA is promised. The verified runtime and the unverified manifest ranges are listed separately in the package reference.

Security reporting

Do not disclose security-sensitive information in a public issue or pull request. Use the repository owner's configured private vulnerability-reporting channel or an existing authorized private project channel. No new email address or public contact is published here because one has not been approved and verified.

Before public release, the owner must configure the channel, name the supported versions, define response targets and update this page. Never include secrets, tokens, customer data or exploit payloads in an unconfirmed channel.

Release gate

For a beta release, tag versioned artifacts and verify clean installation and upgrades without path repositories. The release checklist should verify anonymous Composer metadata, immutable downloads and package isolation. Document the supported version constraints, support scope and security-reporting channel with the release.