Release Policy

DBFlow packages follow transparent versioning during alpha. This page explains what to expect from tagged releases.

Versioning

Today all published DBFlow packages are in alpha. There is no stable 1.0 release yet.

Breaking changes

Alpha releases may contain breaking changes without a major version bump.

Examples during alpha:

• JSON workflow definition schema adjustments
• Renamed config keys or service provider hooks
• Filament page or resource slug changes
• Stricter validation on workflow definitions

Mitigation:

• Pin exact Composer tags in composer.json (for example 0.1.0-alpha.1)
• Read release notes before upgrading alpha tags
• Run your workflow integration tests after every package update

Upgrade notes

Each tagged release on GitHub should include release notes covering:

• Added, changed, and removed APIs
• Migration or config changes
• Known issues

If a release note is missing for a tag you depend on, open a GitHub issue before upgrading.

Pro compatibility

dbflowlabs/filament-pro depends on Core and Filament Standard.

• Pro preview builds target the same PHP, Laravel, and Filament baseline documented in Package Status
• Upgrade Core and Filament Standard before upgrading Pro in preview environments
• Pro-generated definitions must remain compatible with the Core runtime JSON schema

Security

Report security vulnerabilities privately — do not open public GitHub issues for exploit details.

Email: [email protected]

Include:

• Affected package and version
• Steps to reproduce
• Impact assessment if known

We aim to acknowledge reports within a reasonable window during alpha. There is no paid security SLA today.

Support channels during alpha

Related

• Package Status — maturity and compatibility matrix
• Roadmap — what the team is working on next