Release Policy

DBFlow packages follow semantic versioning from 1.0.0 onward. This page explains what to expect from tagged releases.

Versioning

Stage	Tag pattern	Expectations
Stable	`1.x` (current 1.1)	Semver for public API; migration guides for majors and notable minors
Prerelease	`1.0.0-rc.*`, `0.x` (historical)	Used before 1.0; see GitHub release notes

All published DBFlow packages reached 1.0 stable on 2026-07-07 (first stable tag 1.0.0). The current coordinated line is 1.1.0 (2026-07-23 / 2026-07-24). Use ^1.1 constraints in production.

Context	Write this	Example
Product / docs copy	1.1 / 1.x stable	"DBFlow Pro is on 1.1"
`composer require`	`^1.1`	`dbflowlabs/filament-pro:^1.1`
Git tag, OSS path, `package_releases.version`	`1.1.0`	`releases/.../1.1.0/...`

Breaking changes

1.x stable releases follow semver: breaking public API changes require a major version bump. Minor releases such as 1.1 are additive.

0.x prerelease history may contain breaking changes without a major bump. If you still depend on 0.1.0-alpha.* tags, upgrade via UPGRADE-1.0 before moving to ^1.0, then Upgrade to 1.1.

Mitigation:

Prefer composer require dbflowlabs/core:^1.1 (and matching Filament / Pro constraints)
Read GitHub release notes before upgrading
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

Start with Upgrade to 1.1 when moving from 1.0.x. 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 at ^1.1.

Pro builds target the same PHP, Laravel, and Filament baseline documented in Package Status
Upgrade Core and Filament Standard before upgrading Pro
Pro-generated definitions must remain compatible with the Core runtime JSON schema (1.0 or additive 1.1)

Security

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

Email: hello@dbflow.dev

Include:

Affected package and version
Steps to reproduce
Impact assessment if known

Support channels

Channel	Best for
GitHub Issues	Bugs, docs gaps, integration questions
Documentation	Installation, API reference, examples
Email	Pro licensing, Composer access, security

Package Status — maturity and compatibility matrix
Upgrade to 1.1