Skip to main content
nexlem

Migration Guide: v2.1 to v2.2

Note: v2.2 is Nexlem's first public release. There is no installed base of v2.1 consumers in the field. This document serves as a format-demonstration instance of docs/migrations/TEMPLATE.md, and documents what genuinely changed between the v2.1 internal milestone and v2.2. It does not invent migration steps for consumers who do not exist.

Summary

v2.2 is the first public release of Nexlem. It introduces the nexlem-sdk binary and the formal stability contract for the query interface. If you are installing Nexlem for the first time, follow docs/GETTING_STARTED.md — this is an install, not an upgrade.

Breaking Changes

None — this is the first public release. There is no prior installed base to migrate from.

ChangeBefore (v2.1)After (v2.2)Action Required
—v2.1 was an internal milestone, not a public releasev2.2 is the first public releaseInstall fresh per GETTING_STARTED.md

What Changed Between the v2.1 Milestone and v2.2

These are the genuine changes introduced in the v2.2 release cycle, for the record:

nexlem-sdk binary introduction

The nexlem-sdk command-line binary was formalized as the primary automation interface in v2.2. It exposes the query namespace for scripted access to Nexlem state and health checks. Prior to v2.2, the binary existed but was not documented or classified by stability tier.

Local-tarball install path

Nexlem is distributed as a local tarball until v2.3, at which point it will be published to npm. Build the tarball with bun pm pack and install it into your content project with bun add <tarball>, as documented in docs/GETTING_STARTED.md. npm registry publication (npm install @nexlem/framework) is planned for v2.3.

Stability contract

v2.2 publishes the first formal stability contract in docs/STABILITY.md, classifying the nexlem-sdk query handlers into stable and evolving tiers. See that document for the full contract and deprecation policy.

Step-by-step

There are no migration steps — v2.2 is the first public release. New installations follow docs/GETTING_STARTED.md.

Edit this page on GitHub