release notes

versioning scheme

dframework uses a structured versioning scheme designed for consistency across all subsystems.

version structure

version numbers follow the standard three segment format:

1major.minor.patch

during the pre-1.0 series (0.x releases), the framework treats minor increments as major architectural boundaries:

• 0.X.0 (minor increment): serves as a major release. it introduces major new features, architectural refinements, and may contain breaking changes.
• 0.X.Y (patch increment): represents maintenance, bug fixes, performance optimizations, and non breaking refinements.

after the 1.0 milestone, standard semantic versioning applies where only major version bumps contain breaking changes.

major versions

major versions are released when substantial improvements or core capability additions are introduced.

because dframework maintains a closed world architecture where routing, templating, styling, database management, and native compilation work as a cohesive unit, major versions advance the entire platform simultaneously.

minor and patch versions

minor and patch versions never contain breaking changes. they are strictly backwards compatible within the same release series.

patch releases focus on:

• bug fixes in core subsystems
• performance and memory optimizations
• compiler and build pipeline hardening
• native bridge reliability fixes
• security hardening and dependency maintenance

applications can safely update to newer patch versions without modifying application code or database schemas.

support policy

dframework provides support focused on the latest release series to ensure development efforts remain focused.

active support

active support is provided exclusively for the latest release series. all bug fixes, improvements, and performance enhancements are applied directly to the active branch and published as patch releases.

earlier release series do not receive backported bug fixes. when encountering an issue in an earlier version, the standard resolution is upgrading to the latest release.

security fixes

security vulnerabilities are investigated and resolved with highest priority. security patches are published immediately for the active release series.

if a critical vulnerability is identified, a patch release is published and users are advised to update their deployments.

forward evolution

dframework follows a strict forward evolution philosophy. legacy compatibility shims and deprecated adapter layers are avoided because they add runtime overhead and complicate internal code paths.

when an architectural convention is improved, applications are expected to migrate forward to the new pattern.

stability guarantees

unified package consistency

dframework ships as a single, fully integrated package. all framework components (including the server runtime, active record orm, compiled view engine, client styling system, dspa router, worker queue, scheduler, cli tools, and native bridge) are versioned and released together.

cross platform runtime parity

native shell runtimes (ios swift, android kotlin, and desktop tauri rust) are integrated directly into the framework package. the native bridge protocol and js reference implementations are tested and verified against all supported platforms on every release.

upgrading applications

upgrade path

to upgrade an existing application to the latest patch release within your current series, update the package version in package.json and reinstall dependencies:

1npm install dframework@latest

after updating, restart the application server to compile assets and verify runtime operation:

1dstrn serve

breaking change notices

when moving between major releases (such as 0.21 to 0.22), review the changelog for breaking change notices and migration steps before updating production systems.