Skip to main content
The Resolid Framework uses Changesets to manage versioning and changelogs across all packages in the monorepo.

​
Viewing Changes

Each package maintains its own changelog that documents all version updates, new features, bug fixes, and breaking changes.

GitHub Releases

View all releases and their detailed changelogs on GitHub

Package Changelogs

Browse individual CHANGELOG.md files for each package

​
Core Packages

The framework consists of several core packages, each with its own changelog:
Dependency injection container for managing application dependencies.View Changelog
Event management and handling system.View Changelog
Caching utilities and implementations.View Changelog
File-based caching implementation.View Changelog
Development tools and utilities.View Changelog

​
Understanding Changelog Format

Changelogs follow the Keep a Changelog format with semantic versioning:
Breaking changes that require migration steps.Example:
## 1.0.0

### Major Changes

- refactor(core): remove old container API

BREAKING CHANGE: the previous `createContainer` method is replaced with a new interface

​
Staying Updated

1

Watch the repository

Watch the repository on GitHub to receive notifications about new releases.
2

Check release notes

Review the releases page for detailed information about each version.
3

Follow migration guides

For breaking changes, follow the migration guides provided in the release notes.
4

Update dependencies

Keep your dependencies up to date using your package manager:
pnpm update @resolid/*
The changelog is automatically generated from commit messages following the Conventional Commits specification.

Build docs developers (and LLMs) love

Get started for freeTalk to us