---
title: "Release Model"
description: "How RoomSharp versions its multi-package ecosystem and stabilization releases."
canonical: "https://roomsharp.dev/docs/v0.5.4/release-model"
source: "src/content/v0.5.4/release-model.mdx"
---

# Release Model

RoomSharp is a multi-package ecosystem, not a single package.

The ecosystem includes the core runtime, source generator, database providers, dependency injection integration, query extensions, reactive extensions, WinForms bindings, and CLI tooling.

## Synchronized Versioning

Starting with `v0.5.3`, RoomSharp uses synchronized versioning across ecosystem packages.

Packages released as part of the same ecosystem update share the same version number. This makes the ecosystem easier to consume and reduces confusion around runtime, provider, CLI, and extension compatibility.

When using multiple RoomSharp packages together, keep them on the same version whenever possible.

<Note>
`RoomSharp.QueryExtensions` may use its own package version when its release cadence differs, but its documentation still records which RoomSharp release line it was designed and tested with.
</Note>

## Stabilization Releases

Feature releases may be followed by short stabilization cycles.

The `0.5.x` line focuses on stability, provider behavior, generated-code consistency, and production polish following the Smart Entity Lifecycle work introduced in `v0.5.0`.

Because RoomSharp spans generated code, runtime behavior, database providers, CLI tooling, and extensions, a patch release may stabilize behavior across multiple layers at once.

A patch release does not necessarily mean every package received a major internal change. Some packages may be released to keep the ecosystem aligned.

## Release Philosophy

RoomSharp aims for fast development, but disciplined releases.

The goal is to keep the ecosystem moving while preserving correctness, provider compatibility, generated-code consistency, and long-term maintainability.

<Tip>
For day-to-day consumption, prefer matching package versions across the RoomSharp ecosystem, then use the [Changelog](/docs/v0.5.4/changelog) to see which layer changed in each release.
</Tip>