Release Strategy

We follow semantic versioning in Reshaped, using a major.minor.patch format for version numbers.

  • Major releases: Include new features that affect how Reshaped integrates into your product. This can involve changes to the component properties API, component naming, or visually breaking changes. Updating to this version will require changes to your product, but we provide migration guidelines for every major release.
  • Minor releases: Introduce new features that do not break your product. These releases can visually update your application but don’t require any code refactoring to update the library.
  • Patch releases: Include bug fixes and smaller changes. No product code changes are required to update the library.

We maintain at least a 12-month gap between major releases.

To focus on developing new features and ensuring high quality, we provide limited support for outdated major releases while offering guidelines for smoother migration to the latest versions.

  • Latest major release: Active development and complete support.
  • Previous major release: Critical bug fixes only.